dbcve.org
Json.hApplication · Json.h Project

CVE-2022-45492

HIGH · 7.8 CVSS v3.1 Published 2023-02-03
Fix available
A fix is available. Upgrade to 2022-11-14 or later.
See remediation →
80/100
Remediation priority · High
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
Buffer overflow vulnerability in function json_parse_number in sheredom json.h before commit 0825301a07cbf51653882bf2b153cc81fdadf41 (November 14, 2022) allows attackers to code arbitrary code and gain escalated privileges.

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

A buffer overflow vulnerability exists in the json_parse_number function of the sheredom json.h library, a lightweight C JSON parser. The flaw allows an attacker to overwrite adjacent memory regions, potentially achieving arbitrary code execution with elevated privileges.

MitigationUpdate the sheredom json.h library to a version after commit 0825301a07cbf51653882bf2b153cc81fdadf41 (November 14, 2022) or apply the specific commit fix to remediate the vulnerability.

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.hApplication
Affected:< 2022-11-14

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

CVSS:3.1/AV:L/AC:L/PR:L/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 json.h in your codebase
    Search for the file 'json.h' in your project directories, typically in include folders or third-party libraries. Identify if it originates from the sheredom json.h project (check for sheredom copyright or project references in file comments).
    Affected if The file is present and originates from sheredom json.h library
  2. Check json.h version or date
    Open the json.h file and look at the header comments for version information or date. Also check the file modification timestamp. The vulnerability affects versions before November 14, 2022.
    Affected if The json.h version date is before 2022-11-14 or no version date is visible and the file predates that release
  3. Identify json_parse_number usage
    Search your codebase for calls to json_parse or any JSON parsing functions that would invoke json_parse_number internally. Also check if json_parse_number itself is directly called.
    Affected if Your code parses JSON numbers (any numeric values in JSON input) using this library
  4. Verify buffer handling in json_parse_number
    Inspect the json_parse_number function in your json.h file around line ranges where number parsing occurs. Look for inadequate buffer length checks before copy operations.
    Affected if The function lacks proper bounds checking before buffer writes when parsing numeric strings (unpatched versions)
  5. Check for user-controlled JSON input
    Determine if your application accepts JSON from untrusted sources (user input, network, files from external sources) that gets processed by json_parse.
    Affected if JSON data from untrusted or remote sources is parsed by this library

You are affected if your codebase contains an unpatched sheredom json.h version predating November 14, 2022, and you parse JSON containing numeric values from external or untrusted sources.

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
Upgrade available Upgrade to 2022-11-14 or later
Fixed in 2022-11-14
Interim mitigation

Update the sheredom json.h library to a version after commit 0825301a07cbf51653882bf2b153cc81fdadf41 (November 14, 2022) or apply the specific commit fix to remediate the vulnerability.

Recommended fix High confidence

Upgrade to json.h version from commit 0825301a07cbf51653882bf2b153cc81fdadf41 (November 14, 2022) or later

  1. 1. Identify the json.h file in your project codebase
  2. 2. Check the current version/comment in json.h - look for the version string near the top of the file (typically contains a date or version comment)
  3. 3. Download the updated json.h from the sheredom/json.h repository at github.com/sheredom/json.h
  4. 4. Replace the existing json.h file with the updated version that includes the fix from commit 0825301a07cbf51653882bf2b153cc81fdadf41 (dated November 14, 2022 or later)
  5. 5. Rebuild your project to incorporate the patched library
  6. 6. Test that your JSON parsing functionality works correctly with the updated library
Caveat Minimal - this is a bug fix in a parsing library; verify your application handles valid JSON correctly after upgrade

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

Fix this in Json.h Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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