CVE-2025-3588
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability, which was classified as problematic, has been found in joelittlejohn jsonschema2pojo 1.2.2. This issue affects the function apply of the file org/jsonschema2pojo/rules/SchemaRule.java of the component JSON File Handler. The manipulation leads to stack-based buffer overflow. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceStack-based buffer overflow in jsonschema2pojo 1.2.2's JSON file handler within the apply function of SchemaRule.java. The vulnerability occurs during JSON parsing where fixed-size buffers are improperly handled, allowing local attackers to overflow stack memory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify jsonschema2pojo versionLocate the jsonschema2pojo JAR file in your project dependencies (Maven pom.xml, Gradle build.gradle, or the lib directory). Check the exact version number of the jsonschema2pojo library present in your runtime classpath.Affected if The installed version is 1.2.2 or matches the version containing the vulnerable SchemaRule.java apply function
-
Confirm JSON schema file processingReview application code to determine whether jsonschema2pojo is actively being used to parse or process JSON schema files. Look for imports of org.jsonschema2pojo and calls to methods such as Jsonschema2Pojo.generate() or similar entry points.Affected if Your application uses jsonschema2pojo to process JSON schema files with the affected library version
-
Locate SchemaRule class in classpathSearch the jsonschema2pojo JAR in your application classpath for SchemaRule.class. You can inspect the JAR contents using 'jar tf jsonschema2pojo-*.jar' or a ZIP utility.Affected if SchemaRule.class exists in the jsonschema2pojo library version you are using
-
Identify apply function invocationCheck if your application code or any dependent library directly or indirectly invokes the apply method of SchemaRule during JSON schema parsing. Search code for SchemaRule usage patterns or enable debug logging if available.Affected if The apply function in SchemaRule.java is being called to process JSON schemas with the vulnerable version
You are affected if jsonschema2pojo version 1.2.2 (or the vulnerable version range) is in your classpath and your application processes JSON schema files using this library.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of jsonschema2pojo; until then, avoid processing untrusted JSON schema files with the affected library version.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3588 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-3588 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data