Json Patch
Monthly
Improper access controls in java-json-tools json-patch (versions up to 1.13) allow low-privileged, network-accessible attackers to abuse the CopyOperation.apply and MoveOperation.apply methods to reference JSON document paths outside their permitted scope, enabling unauthorized data reads or writes within the processed JSON structure. The flaw resides in src/main/java/com/github/fge/jsonpatch/CopyOperation.java and affects any application that exposes JSON Patch processing to partially-trusted callers without additional server-side path validation. A public proof-of-concept exists via GitHub issue #170; no CISA KEV listing has been recorded, and the CVSS 4.0 score of 5.3 reflects the limited C/I impact and mandatory low-privilege prerequisite.
Uncontrolled resource consumption in java-json-tools json-patch up to version 1.13 allows remote unauthenticated attackers to trigger service degradation by sending crafted JSON Patch documents to the JsonPatch.apply() handler. The vulnerability resides in the Patch Operation Handler component and carries no confidentiality or integrity impact - purely availability. A public proof-of-concept has been disclosed via a GitHub issue report, though no KEV listing indicates active exploitation at this time.
Stack exhaustion in java-json-tools json-patch ≤1.13 enables remote unauthenticated denial of service by submitting a crafted deeply-nested JSON Merge Patch document to any application endpoint that invokes JsonMergePatch.fromJson. The vulnerability triggers an uncontrolled recursive deserialization path in JsonMergePatchDeserializer.java, causing JVM thread stack exhaustion. The CVSS 4.0 vector (VC:N/VI:N/VA:L) confirms the impact is limited to availability; no confidentiality or integrity impact has been identified. A public exploit/proof-of-concept exists in the GitHub issue tracker, and no patched release version has been independently confirmed.
An out of bound write can occur when patching an Openshift object using the 'oc patch' functionality in OpenShift Container Platform before 3.7. Rated high severity (CVSS 7.7), this vulnerability is remotely exploitable, low attack complexity. This Out-of-bounds Write vulnerability could allow attackers to write data beyond allocated buffer boundaries leading to code execution or crashes.
Improper access controls in java-json-tools json-patch (versions up to 1.13) allow low-privileged, network-accessible attackers to abuse the CopyOperation.apply and MoveOperation.apply methods to reference JSON document paths outside their permitted scope, enabling unauthorized data reads or writes within the processed JSON structure. The flaw resides in src/main/java/com/github/fge/jsonpatch/CopyOperation.java and affects any application that exposes JSON Patch processing to partially-trusted callers without additional server-side path validation. A public proof-of-concept exists via GitHub issue #170; no CISA KEV listing has been recorded, and the CVSS 4.0 score of 5.3 reflects the limited C/I impact and mandatory low-privilege prerequisite.
Uncontrolled resource consumption in java-json-tools json-patch up to version 1.13 allows remote unauthenticated attackers to trigger service degradation by sending crafted JSON Patch documents to the JsonPatch.apply() handler. The vulnerability resides in the Patch Operation Handler component and carries no confidentiality or integrity impact - purely availability. A public proof-of-concept has been disclosed via a GitHub issue report, though no KEV listing indicates active exploitation at this time.
Stack exhaustion in java-json-tools json-patch ≤1.13 enables remote unauthenticated denial of service by submitting a crafted deeply-nested JSON Merge Patch document to any application endpoint that invokes JsonMergePatch.fromJson. The vulnerability triggers an uncontrolled recursive deserialization path in JsonMergePatchDeserializer.java, causing JVM thread stack exhaustion. The CVSS 4.0 vector (VC:N/VI:N/VA:L) confirms the impact is limited to availability; no confidentiality or integrity impact has been identified. A public exploit/proof-of-concept exists in the GitHub issue tracker, and no patched release version has been independently confirmed.
An out of bound write can occur when patching an Openshift object using the 'oc patch' functionality in OpenShift Container Platform before 3.7. Rated high severity (CVSS 7.7), this vulnerability is remotely exploitable, low attack complexity. This Out-of-bounds Write vulnerability could allow attackers to write data beyond allocated buffer boundaries leading to code execution or crashes.