CVE-2022-22968Network attack vector

Integrity bypass via case-sensitive field matching

Published Apr 14, 2022 · Updated Aug 3, 2024

Improper handling of case sensitivity in Spring Framework 5.3.0 through 5.3.18 and 5.2.0 through 5.2.20 allows remote attackers to alter disallowed fields via crafted request parameters. DataBinder disallowedFields matching compares field and nested-property names case-sensitively, so a differently cased parameter bypasses the denylist during MVC or WebFlux binding. Exploitation requires an application using those binders and disallowed field patterns; impact is limited to unauthorized property binding and resulting integrity changes.

CVSS severity3.1
Low
EPSS probability5.67%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper handling of case sensitivity in Spring Framework 5.3.0 through 5.3.18 and 5.2.0 through 5.2.20 allows remote attackers to alter disallowed fields via crafted request parameters. DataBinder disallowedFields matching compares field and nested-property names case-sensitively, so a differently cased parameter bypasses the denylist during MVC or WebFlux binding. Exploitation requires an application using those binders and disallowed field patterns; impact is limited to unauthorized property binding and resulting integrity changes.

The record

CVE
CVE-2022-22968
Published
Apr 14, 2022
Updated
Aug 3, 2024
Vendor
Spring
Product
Spring Framework
Classifications
CWE-178, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 14, 2022CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Spring · Spring Frameworkversion=Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions

Published CVSS scores

3.1SpringCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-178Improper Handling of Case Sensitivity
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo