CVE-2024-22257

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.0% (59th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In Spring Security, versions 5.7.x prior to 5.7.12, 5.8.x prior to 5.8.11, versions 6.0.x prior to 6.0.9, versions 6.1.x prior to 6.1.8, versions 6.2.x prior to 6.2.3, an application is possible vulnerable to broken access control when it directly uses the AuthenticatedVoter#vote passing a null Authentication parameter.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
52
EG Risk 52/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.0%
EPSS %ILE
60th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 18, 2024

Last Modified

June 30, 2026

Advisory Details (3)

Auto-updated Jun 30, 2026
Patch available.
generic

CVE-2024-22257: Possible Broken Access Control in Spring Security With Direct Use of AuthenticatedVoter

https://spring.io/security/cve-2024-22257
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20240419-0005/
generic

CVE-2024-22257: executable affected-version evidence for dependency-check · Issue #8642 · dependency-check/DependencyCheck · GitHub

https://github.com/dependency-check/DependencyCheck/issues/8642

Vendor Advisories for CVE-2024-22257(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpatch2024-07-25redhat
redhatpatch2024-06-06redhat
redhatpatch2024-05-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.springframework.security:spring-security-core6.2.0, 6.2.1, 6.2.2
  • every version up to 5.7.12: fixed in 5.7.12
  • 5.8.0 up to 5.8.11: fixed in 5.8.11
  • 6.0.0 up to 6.1.8: fixed in 6.1.8
  • 6.2.0 up to 6.2.3: fixed in 6.2.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 197 total refreshes for this CVE.

  1. 2026-10-09 20:05 UTCEPSS rescore
  2. 2026-10-08 17:07 UTCEPSS rescore
  3. 2026-10-07 23:46 UTCEPSS rescore
  4. 2026-10-06 15:15 UTCEPSS rescore
  5. 2026-10-05 17:41 UTCEPSS rescore
  6. 2026-10-04 23:20 UTCEPSS rescore
  7. 2026-10-03 14:23 UTCEPSS rescore
  8. 2026-10-01 19:48 UTCEPSS rescore
  9. 2026-09-30 16:57 UTCEG score recompute
  10. 2026-09-30 15:01 UTCEPSS rescore
  11. 2026-09-29 15:17 UTCEPSS rescore
  12. 2026-09-28 13:49 UTCEPSS rescore
  13. 2026-09-24 14:01 UTCEPSS rescore
  14. 2026-09-23 13:46 UTCEPSS rescore
  15. 2026-09-23 13:46 UTCEPSS rescore
  16. 2026-09-20 20:14 UTCEPSS rescore
  17. 2026-09-16 14:06 UTCEPSS rescore
  18. 2026-09-16 05:11 UTCEPSS rescore
  19. 2026-09-15 03:08 UTCEPSS rescore
  20. 2026-09-13 16:45 UTCEPSS rescore
  21. 2026-09-12 14:59 UTCEPSS rescore
  22. 2026-09-11 14:51 UTCEPSS rescore
  23. 2026-09-11 09:34 UTCEPSS rescore
  24. 2026-09-08 21:58 UTCEPSS rescore
  25. 2026-09-07 15:59 UTCEPSS rescore
Show 75 more
  1. 2026-09-06 13:46 UTCEPSS rescore
  2. 2026-09-05 15:26 UTCEPSS rescore
  3. 2026-09-04 13:58 UTCEPSS rescore
  4. 2026-09-04 05:05 UTCEPSS rescore
  5. 2026-09-02 14:10 UTCEPSS rescore
  6. 2026-09-01 13:52 UTCEPSS rescore
  7. 2026-08-30 19:15 UTCEPSS rescore
  8. 2026-08-30 01:20 UTCEPSS rescore
  9. 2026-08-28 21:39 UTCEPSS rescore
  10. 2026-08-27 14:23 UTCEPSS rescore
  11. 2026-08-26 14:44 UTCEPSS rescore
  12. 2026-08-25 13:47 UTCEPSS rescore
  13. 2026-08-23 00:17 UTCEPSS rescore
  14. 2026-08-21 23:47 UTCEPSS rescore
  15. 2026-08-20 22:53 UTCEPSS rescore
  16. 2026-08-19 17:02 UTCEPSS rescore
  17. 2026-08-18 13:46 UTCEPSS rescore
  18. 2026-08-17 13:45 UTCEPSS rescore
  19. 2026-08-16 14:54 UTCEPSS rescore
  20. 2026-08-16 14:54 UTCEPSS rescore
  21. 2026-08-16 02:12 UTCEPSS rescore
  22. 2026-08-15 01:28 UTCEPSS rescore
  23. 2026-08-13 21:58 UTCEPSS rescore
  24. 2026-08-12 13:49 UTCEPSS rescore
  25. 2026-08-11 13:40 UTCEPSS rescore
  26. 2026-08-09 13:45 UTCEPSS rescore
  27. 2026-08-08 16:35 UTCEPSS rescore
  28. 2026-08-06 13:45 UTCEPSS rescore
  29. 2026-08-05 19:15 UTCEPSS rescore
  30. 2026-08-04 15:08 UTCEPSS rescore
  31. 2026-08-04 10:36 UTCEPSS rescore
  32. 2026-08-03 10:34 UTCEPSS rescore
  33. 2026-08-02 02:25 UTCEPSS rescore
  34. 2026-08-02 02:25 UTCEPSS rescore
  35. 2026-08-01 04:14 UTCEPSS rescore
  36. 2026-07-30 16:26 UTCEPSS rescore
  37. 2026-07-30 01:29 UTCEPSS rescore
  38. 2026-07-28 15:34 UTCEPSS rescore
  39. 2026-07-27 14:11 UTCEPSS rescore
  40. 2026-07-26 14:53 UTCEPSS rescore
  41. 2026-07-25 14:16 UTCEPSS rescore
  42. 2026-07-24 14:16 UTCEPSS rescore
  43. 2026-07-23 14:17 UTCEPSS rescore
  44. 2026-07-23 14:17 UTCEPSS rescore
  45. 2026-07-23 02:33 UTCEG score recompute
  46. 2026-07-22 23:20 UTCEG score recompute
  47. 2026-07-22 14:07 UTCEPSS rescore
  48. 2026-07-21 15:23 UTCEPSS rescore
  49. 2026-07-21 15:23 UTCEPSS rescore
  50. 2026-07-20 17:06 UTCEPSS rescore
  51. 2026-07-19 14:30 UTCEPSS rescore
  52. 2026-07-19 14:30 UTCEPSS rescore
  53. 2026-07-19 02:28 UTCEPSS rescore
  54. 2026-07-19 02:28 UTCEPSS rescore
  55. 2026-07-18 10:03 UTCEPSS rescore
  56. 2026-07-18 10:03 UTCEPSS rescore
  57. 2026-07-15 16:56 UTCEPSS rescore
  58. 2026-07-15 16:56 UTCEPSS rescore
  59. 2026-07-15 01:59 UTCEPSS rescore
  60. 2026-07-15 01:59 UTCEPSS rescore
  61. 2026-07-13 22:28 UTCEPSS rescore
  62. 2026-07-13 06:11 UTCEPSS rescore
  63. 2026-07-13 06:11 UTCEPSS rescore
  64. 2026-07-12 05:45 UTCEPSS rescore
  65. 2026-07-11 08:26 UTCEPSS rescore
  66. 2026-07-09 19:09 UTCEPSS rescore
  67. 2026-07-09 19:09 UTCEPSS rescore
  68. 2026-07-08 15:13 UTCEPSS rescore
  69. 2026-07-07 13:45 UTCEPSS rescore
  70. 2026-07-07 13:45 UTCEPSS rescore
  71. 2026-07-06 16:26 UTCEPSS rescore
  72. 2026-07-06 02:22 UTCEPSS rescore
  73. 2026-07-06 02:22 UTCEPSS rescore
  74. 2026-07-05 02:29 UTCEPSS rescore
  75. 2026-07-04 06:30 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-22257?
CVE-2024-22257 is a high vulnerability published on March 18, 2024. In Spring Security, versions 5.7.x prior to 5.7.12, 5.8.x prior to 5.8.11, versions 6.0.x prior to 6.0.9, versions 6.1.x prior to 6.1.8, versions 6.2.x prior to 6.2.3, an application is possible vulnerable to broken access control when it directly uses the AuthenticatedVoter#vote passing a null…
When was CVE-2024-22257 disclosed?
CVE-2024-22257 was first published on March 18, 2024, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-22257 actively exploited?
CVE-2024-22257 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (60th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-22257?
CVE-2024-22257 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2024-22257?
A fix for CVE-2024-22257 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-22257 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-22257

Explore →

Is Your Infrastructure Affected by CVE-2024-22257?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs