CVE-2024-42363
Published: 20 August 2024
Summary
CVE-2024-42363 is a high-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Github (inferred from references). Its CVSS base score is 8.8 (High).
Operationally, ranked in the top 15.0% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2024-42363 is a deserialization vulnerability (CWE-502) in Zendesk Samson prior to commit 3385. In the Kubernetes plugin, a user-supplied role parameter reaches the RoleVerificationsController, flows into the RoleConfigFile initializer, and is passed to Kubernetes::Util.parse_file, where it is processed by the unsafe YAML.load_stream method. The flaw carries a CVSS 3.1 score of 8.8.
An attacker with low-privileged network access and no user interaction can submit a crafted role value to trigger arbitrary code execution, resulting in full compromise of confidentiality, integrity, and availability on the affected Samson instance.
The vulnerability is addressed in commit 3385, delivered via pull request 4071, which removes the unsafe YAML deserialization path for the role parameter.
The associated EPSS score rose from a low baseline to a peak of 0.0512 before receding to its current value of 0.0227, indicating transient post-disclosure interest that has since declined.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-39572
Vulnerability details
Prior to 3385, the user-controlled role parameter enters the application in the Kubernetes::RoleVerificationsController. The role parameter flows into the RoleConfigFile initializer and then into the Kubernetes::Util.parse_file method where it is unsafely deserialized using the YAML.load_stream method. This issue may lead…
more
to Remote Code Execution (RCE). This vulnerability is fixed in 3385.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Penetration testing supplies malicious serialized objects, detecting unsafe deserialization and supporting corrective actions.
Evaluation of untrusted data handling (deserialization testing) reveals unsafe processing, which the required remediation process addresses.
Untrusted serialized data can be deserialized and observed inside the chamber, blocking gadget-chain exploitation outside the sandbox.
Validates or rejects untrusted serialized data before deserialization occurs.
Identifies and blocks malicious code introduced through deserialization of untrusted data at system boundaries.
Integrity verification of serialized information can detect tampering before deserialization occurs.
Provenance of associated data allows detection of untrusted sources before deserialization or processing occurs.