dbcve.org
Json\+\+Application · Hjiang

CVE-2022-23459

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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 use of the Value class may lead to memory corruption via a double free or via a use after free. The value class has a default assignment operator which may be used with pointer types which may point to alterable data where the pointer itself is not updated. This issue exists on the current commit of the jsonxx project. The project itself has been archived and 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 · moderate confidence

Memory corruption vulnerability in jsonxx's Value class where the default assignment operator, when used with pointer types, can lead to double-free or use-after-free conditions. The pointer points to alterable data but the pointer itself isn't properly updated during assignment.

MitigationSince the project is archived and no patches are expected, migrate to an actively maintained C++ JSON library (e.g., nlohmann/json, RapidJSON, or simdjson).

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Locate jsonxx library files
    Search for jsonxx header files (e.g., json.h, json.hpp, value.h) or library binaries in your project dependencies, build output, or installed paths
    Affected if jsonxx headers or library files are present in the environment
  2. Determine installed jsonxx version
    Inspect the version string in jsonxx header files (typically in json.h or version.h) or check the library filename (e.g., libjsonxx.so.1.0.0)
    Affected if The version is 1.0.0 or 1.0.1
  3. Identify code using Value class with pointers
    Search source code for declarations or assignments involving jsonxx::Value with pointer types (e.g., Value* ptr = new Value(); ... = *ptr;) where the pointer points to dynamically allocated memory
    Affected if Code uses Value pointers that are assigned to one another, triggering the default assignment operator
  4. Check for assignment operator usage in runtime code
    Review application code for patterns where Value pointer objects are assigned to each other after construction, which invokes the vulnerable assignment operator
    Affected if Value pointer assignments occur in the codebase after initial construction

You are affected if jsonxx version 1.0.0 or 1.0.1 is present AND your code uses the Value class with pointer types that get assigned to one another.

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 the project is archived and no patches are expected, migrate to an actively maintained C++ JSON library (e.g., nlohmann/json, RapidJSON, or simdjson).

Recommended fix High confidence
  1. Migrate to an actively maintained JSON library for C++ (e.g., nlohmann/json, RapidJSON, or JsonCpp)
  2. Audit existing code using jsonxx for any instances of the double free vulnerability
  3. Replace jsonxx library references in the codebase with the chosen alternative JSON library
  4. Recompile and test the application to ensure functionality is preserved
Caveat Migration to a new JSON library may require API changes and code modifications

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

Fix this in Json\+\+ Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23459 — 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-23459 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