dbcve.org
Json\+\+Application · Hjiang

CVE-2022-23460

HIGH · 7.5 CVSS v3.1 Published 2022-08-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Jsonxx or Json++ is a JSON parser, writer and reader written in C++. In affected versions of jsonxx json parsing may lead to stack exhaustion in an address sanitized (ASAN) build. This issue may lead to Denial of Service if the program using the jsonxx library crashes. This issue exists on the current commit of the jsonxx project and the project itself has been archived. Updates are not expected. Users are advised to find a replacement.

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 · high confidence

Jsonxx C++ JSON parser has a stack exhaustion vulnerability during JSON parsing in ASAN-enabled builds. The parser likely uses deep recursion for nested JSON structures, causing stack overflow that crashes the program and leads to denial of service.

MitigationSince jsonxx is archived with no updates, users must migrate to an active JSON library or implement input validation/length limits on JSON data before parsing to prevent stack exhaustion.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Json\+\+Application
Affected:= 1.0.0= 1.0.1

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify jsonxx library in use
    Search your project dependencies, build artifacts, or installed packages for 'jsonxx' or 'Json++'. Check your package manager, package.json, CMakeLists.txt, Makefile, or similar dependency files.
    Affected if jsonxx is found as a dependency or included library
  2. Determine jsonxx version
    Check the version string reported by the library at runtime, or inspect the source/version header file (often version.h or similar) if you have access to the library source.
    Affected if The installed version is exactly 1.0.0 or exactly 1.0.1
  3. Verify JSON parsing of untrusted input
    Inspect your application code to determine if it uses jsonxx to parse JSON data from external or untrusted sources, such as API requests, uploaded files, or network data.
    Affected if Your application uses jsonxx to parse JSON from untrusted or user-controlled sources
  4. Check for deep or recursive JSON structures
    Analyze the JSON data being processed. Determine if it contains deeply nested objects or arrays that could trigger recursive parsing logic.
    Affected if The parsed JSON data can contain deeply nested structures (many levels of objects within objects or arrays within arrays)

You are affected if your environment uses jsonxx version 1.0.0 or 1.0.1 to parse JSON data from untrusted sources that could contain deeply nested structures.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since jsonxx is archived with no updates, users must migrate to an active JSON library or implement input validation/length limits on JSON data before parsing to prevent stack exhaustion.

Recommended fix High confidence
  1. Identify all uses of the jsonxx (json++) library in your codebase
  2. Research and select an alternative JSON parsing library (e.g., nlohmann/json, RapidJSON, jsoncpp, or Poco JSON)
  3. Plan and execute migration from jsonxx to the chosen alternative library
  4. Thoroughly test the migration to ensure JSON parsing functionality works correctly
  5. Remove jsonxx dependency from your project
Caveat Library is archived and unmaintained; migration to alternative JSON library required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Json\+\+ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
23.0 hours of engineering $4,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,400.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23460 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-23460 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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