Skip to content
Server Security Center
KEVcritical9.8

CVE-2016-4437: Apache Shiro Code Execution

Apache Shiro · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.

CVSS v3.1 (CVE record)
9.8
critical
EPSS (exploit probability, 30 days)
93%
higher than 99.8% of all CVEs
Added to CISA KEV
2021-11-03
US federal due date 2022-05-03
Ubuntu priority
high

CVE-2016-4437 explained

CVE-2016-4437 affects Apache Shiro before 1.2.5. When no cipher key is configured for the "remember me" feature, remote attackers can execute arbitrary code or bypass intended access restrictions. The flaw is listed in the CISA Known Exploited Vulnerabilities catalog, so it has been exploited in practice.

Impact

An unauthenticated remote attacker can send a crafted request over the network and run arbitrary code or bypass access controls in an application using a vulnerable Shiro version. No user interaction or privileges are needed and attack complexity is low. Successful exploitation can fully compromise confidentiality, integrity and availability. The condition is that no cipher key has been configured for the "remember me" feature.

Who is affected

Ubuntu 16.04 LTS ships the affected shiro source package. A fixed version, 1.2.4-1ubuntu0.1~esm1, is available through the Ubuntu Pro (ESM) channel. Ubuntu 16.04 LTS is end of life. No other Ubuntu or Debian releases are listed as affected in the available data. Applications that bundle their own copy of Apache Shiro before 1.2.5 are also affected and need their own update.

Written with AI from the data on this page and checked against it automatically.

Official description

Apache Shiro before 1.2.5, when a cipher key has not been configured for the "remember me" feature, allows remote attackers to execute arbitrary code or bypass intended access restrictions via an unspecified request parameter.

CISA required action: Apply updates per vendor instructions.

CISA notes

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. On Ubuntu 16.04 LTS, install shiro version 1.2.4-1ubuntu0.1~esm1 or later from the Ubuntu Pro (ESM) channel.
  2. Restart all Java applications and services that use Shiro so they load the updated library.
  3. Check applications that bundle Apache Shiro and update them to 1.2.5 or later.
  4. Plan an upgrade from Ubuntu 16.04 LTS to a supported release, since it is end of life.
  5. Limit network exposure of affected applications until they are updated.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace shiro with the source package from the table above.

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="shiro"'

2. Compare each installed version with the fixed version for your release from the table

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the fix

sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="shiro"{print $1}')

Services keep running the old code until they are restarted – restart the affected service or check with needrestart.

Rows marked “fix via Ubuntu Pro”: these fixes are only installable with an Ubuntu Pro subscription (ESM). Attach the machine first (sudo pro attach, then sudo pro enable esm-infra esm-apps), then run the commands above.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-321 Use of Hard-coded Cryptographic Key

Questions about CVE-2016-4437

Is this vulnerability exploited in the wild?
Yes. CISA added CVE-2016-4437 to its Known Exploited Vulnerabilities catalog on 2021-11-03. The required action is to apply updates per vendor instructions. Whether it is used in ransomware campaigns is unknown.
Which configuration makes an application vulnerable?
Apache Shiro before 1.2.5 is vulnerable when a cipher key has not been configured for the "remember me" feature. Updating Shiro is the recommended remediation.
Is a restart needed after updating?
Yes. Running Java applications keep using the old library code until they are restarted. Restart every service that loads Shiro after installing the update.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.