Security Resilience

CVE-2023-26819

Cjson Project Cjson 1.7.15

Public PoC
Published
19 April 2025
Modified
03 November 2025
CVSS Score v3.1 2.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0023 13th percentile
Risk Priority 26 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-26819 is a low-severity Expected Behavior Violation (CWE-440) vulnerability in Cjson Project Cjson. Its CVSS base score is 2.9 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked at the 13th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-6 (Security and Privacy Function Verification) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

cJSON 1.7.15 might allow a denial of service via a crafted JSON document such as {"a": true, "b": [ null,9999999999999999999999999999999999999999999999912345678901234567]}.

CWE(s)
CWE-440

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
attack.mitre.org →
T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
attack.mitre.org →
T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
attack.mitre.org →
T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
attack.mitre.org →
T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
attack.mitre.org →
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-31755Same product: Cjson Project Cjson
CVE-2023-53154Same product: Cjson Project Cjson
CVE-2024-8690Shared CWE-440
CVE-2025-27094Shared CWE-440
CVE-2025-13940Shared CWE-440
CVE-2025-52953Shared CWE-440
CVE-2025-40555Shared CWE-440
CVE-2023-32732Shared CWE-440
CVE-2024-56202Shared CWE-440
CVE-2024-38806Shared CWE-440

Affected Assets

cjson project
cjson
1.7.15

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation directly checks whether implemented functions match their specifications.

SI-6 Security and Privacy Function Verification good match

Security function verification confirms that functions operate according to their defined expected behavior.

SA-17 Developer Security and Privacy Architecture and Design partial match

Requiring a documented security architecture and design reduces the chance that implementation deviates from intended behavior.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

ID.IM-02 partial match
blocks

Security testing and exercises help discover behavior deviations before deployment.

ID.RA-01 partial match
blocks

Vulnerability identification can surface spec-violating flaws, while eliminating the weakness reduces some vulnerability backlog.

PR.PS-02 partial match
blocks

Routine software maintenance and patching can remediate discovered specification violations.

PR.PS-06 partial match
blocks

Secure SDLC practices directly enforce specification compliance and catch expected-behavior violations during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.19 Installation of software on operational systems partial match
removes
A.8.25 Secure development life cycle partial match
blocks

Secure development life cycle mandates verification against specifications, directly reducing expected-behavior violations.

A.8.26 Application security requirements partial match
blocks

A.8.26 only requires that security requirements (including resilience against attacks like injections) be identified and specified during development or acquisition; it does not itself enforce, implement or assure those requirements, so the expected-behavior violation can still arise and be exploited.

A.8.27 Secure system architecture and engineering principles partial match
removes
A.8.28 Secure coding partial match
prevents

Secure coding practices enforce adherence to functional specifications during implementation.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing in development and acceptance validates that functions behave as specified.

References