Is CVE-2016-4437 exploited in the wild?

Yes. CVE-2016-4437 is known to be exploited in the wild, first recorded on 3 November 2021. Treat it as urgent.

How severe is CVE-2016-4437?

Critical severity, with a CVSS score of 3.1, published 14 May 2022.

Which products and versions are affected?

org.apache.shiro:shiro-core (Maven) ECOSYSTEM:introduced=0,fixed=1.2.5.

Is there a fix for CVE-2016-4437?

Yes. org.apache.shiro:shiro-core (Maven): upgrade to 1.2.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2016-4437 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2016-4437?

Check whether you run Apache Shiro or org.apache.shiro:shiro-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2016-4437: Improper Access Control in Apache Shiro

CVE-2016-4437 · Severity: critical · CVSS 3.1 · Exploited in the wild · Published 2022-05-14

Apache Shiro before 1.2.5 contains a vulnerability where a default or unconfigured cipher key for the 'remember me' feature allows for the execution of arbitrary code. Remote attackers can exploit this via unspecified request parameters to bypass access restrictions or achieve remote code execution.

Technologies: Apache Shiro, org.apache.shiro:shiro-core (Maven). Vendors: Apache, Maven.

Quick answers

Is CVE-2016-4437 exploited in the wild?: Yes. CVE-2016-4437 is known to be exploited in the wild, first recorded on 3 November 2021. Treat it as urgent.
How severe is CVE-2016-4437?: Critical severity, with a CVSS score of 3.1, published 14 May 2022.
Which products and versions are affected?: org.apache.shiro:shiro-core (Maven) ECOSYSTEM:introduced=0,fixed=1.2.5.
Is there a fix for CVE-2016-4437?: Yes. org.apache.shiro:shiro-core (Maven): upgrade to 1.2.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2016-4437 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2016-4437?: Check whether you run Apache Shiro or org.apache.shiro:shiro-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.apache.shiro:shiro-core (Maven): upgrade to 1.2.5 or later

# set org.apache.shiro:shiro-core to 1.2.5 in your pom.xml or build.gradle

Affected products

Apache Shiro before 1.2.5
Apache Aurora 0.10.0 to 0.18.1
Red Hat Fuse 1.0
Red Hat JBoss Middleware text-only advisories 1.0

Identifiers

CVE-2016-4437
GHSA-p836-389h-j692

Timeline

2016-06-07: disclosed: Initial public disclosure via SecurityFocus and Packet Storm
2021-11-03: kev added: Added to CISA Known Exploited Vulnerabilities Catalog

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.