dbcve.org
Json.hApplication · Json.h Project

CVE-2022-45496

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_string 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

Buffer overflow vulnerability in the json_parse_string function in sheredom json.h library allows attackers to execute arbitrary code and gain escalated privileges. The flaw exists in versions prior to commit 0825301a07cbf51653882bf2b153cc81fdadf41 released November 14, 2022.

MitigationUpdate sheredom json.h to version/commit after 0825301a07cbf51653882bf2b153cc81fdadf41 (November 14, 2022) or later to remediate the buffer overflow in json_parse_string.

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 the json.h header file in your environment
    Search your codebase or include directories for files named 'json.h' - this is a header-only library typically included directly in projects
    Affected if The file is present and is the sheredom json.h library (often in a third_party, vendor, or include folder)
  2. Determine the commit or version of json.h
    Check the file's git history if it's in a git repository, or look for version comments at the top of the header file. The library tracks versions by commit date rather than semantic versioning
    Affected if The library version cannot be determined to be on or after the November 14, 2022 commit (0825301a07cbf51653882bf2b153cc81fdadf41)
  3. Verify the json_parse_string function is being called
    Search your codebase for calls to json_parse_string function - this is the specific function containing the buffer overflow vulnerability
    Affected if Your code directly calls json_parse_string to parse JSON strings
  4. Check if using a bundled or embedded copy of json.h
    Examine your project's dependency manifest, package manager files, or vendored third-party code to see if json.h is bundled
    Affected if You have embedded or vendored a copy of sheredom json.h in your project and that copy predates November 2022

Your environment is affected if you are using a copy of sheredom json.h that was committed or downloaded before November 14, 2022, and your code calls the json_parse_string function to parse untrusted JSON input.

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 sheredom json.h to version/commit after 0825301a07cbf51653882bf2b153cc81fdadf41 (November 14, 2022) or later to remediate the buffer overflow in json_parse_string.

Recommended fix High confidence

json.h from commit 0825301a07cbf51653882bf2b153cc81fdadf41 or later (any version after 2022-11-14)

  1. 1. Locate the current json.h file in your project (typically in an include or third-party directory)
  2. 2. Navigate to the sheredom/json.h GitHub repository at github.com/sheredom/json.h
  3. 3. Download the json.h file from commit 0825301a07cbf51653882bf2b153cc81fdadf41 or any commit after November 14, 2022
  4. 4. Replace the existing vulnerable json.h with the fixed version
  5. 5. Rebuild your project to ensure the new header is compiled
  6. 6. Verify the fix by testing functionality that uses JSON parsing

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-45496 — 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-45496 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