Skip to content
Fencer Intel
high 7.5

CVE-2019-12422 json

Improper input validation in Apache Shiro

published 6y ago modified 4mo ago also GHSA-r679-m633-g7wc , EUVD-2020-0313

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
9.1%
EPSS 9.1% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

Apache Shiro before 1.4.2, when using the default "remember me" configuration, cookies could be susceptible to a padding attack.

Patch / fix

  • maven org.apache.shiro:shiro-core 1.4.2
  • apache shiro 1.4.2

Is CVE-2019-12422 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-12422 updated cvss 7.4

shiro: Cookie padding oracle vulnerability with default configuration

  • Red Hat JBoss A-MQ 6 shiro-core shiro-core Red Hat JBoss Fuse 6 shiro-core shiro-core Red Hat JBoss Fuse Service Works 6 shiro-core shiro-core Red Hat OpenStack Platform 10 (Newton) opendaylight
    affected: no fix planned “Out of support scope”
  • Red Hat OpenStack Platform 13 (Queens) opendaylight Red Hat OpenStack Platform 14 (Rocky) opendaylight
    affected: no fix planned “Will not fix”
  • Red Hat Fuse 7.6.0
    fixed: vendor fix RHSA-2020:0983

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

9.10% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.shiro:shiro-core
<1.4.2
1.4.2

Affected products

  • Apache Shiro

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.