Quick answers
- Is CVE-2023-2251 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2023-2251 being exploited in the wild.
- How severe is CVE-2023-2251?
- Low severity, with a CVSS score of 3.1, published 24 April 2023.
- Which products and versions are affected?
- Yaml SEMVER:introduced=2.0.0-5,fixed=2.2.2.
- Is there a fix for CVE-2023-2251?
- Yes. Yaml: upgrade to 2.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2023-2251 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2023-2251?
- Check whether you run Yaml at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Yaml: upgrade to 2.2.2 or later
Technical details
This is an uncaught exception vulnerability (CWE-248) in eemeli/yaml's error pretty-printer that occurs when handling certain corner cases during YAML parsing. The vulnerability affects versions 2.0.0-5 through 2.2.1 and is triggered when processing specially crafted YAML input that reaches the error reporting code path. The attack is network-accessible with no authentication or user interaction required, as the library processes untrusted YAML data. An attacker can trigger an unhandled exception that crashes the application, resulting in denial of service. The fix was released in version 2.2.2, addressing the corner case failure in the error reporting function.
Affected products
- eemeli yaml 2.0.0-5 to 2.2.1
Identifiers
- CVE-2023-2251
- GHSA-f9xv-q969-pqx4
Timeline
- 2023-04-24: disclosed: Published in GitHub Advisory Database
- 2023-04-24: patched: Fix released in version 2.2.2