CVE-2023-2251: Yaml_project Yaml Exception Vulnerability

CVE-2023-2251 Overview

CVE-2023-2251 is an Uncaught Exception vulnerability discovered in the eemeli/yaml Node.js package, a popular YAML parser and stringifier library. The vulnerability exists in versions prior to 2.0.0-5 and can be exploited remotely by an attacker to cause a denial of service condition by triggering an unhandled exception during YAML processing.

Critical Impact
Remote attackers can cause application crashes and denial of service by exploiting an uncaught exception in the YAML error pretty-printer, potentially disrupting services that rely on this parsing library.

Affected Products

yaml_project yaml (Node.js package) versions prior to 2.0.0-5
Applications using the eemeli/yaml library for YAML parsing
Node.js services that process untrusted YAML input

Discovery Timeline

2023-04-24 - CVE-2023-2251 published to NVD
2024-11-21 - Last updated in NVD database

Technical Details for CVE-2023-2251

Vulnerability Analysis

The vulnerability resides in the error handling mechanism of the YAML parser, specifically within the error pretty-printer functionality in src/errors.ts. When processing malformed YAML input that triggers certain error conditions, the library fails to properly handle edge cases in its error message formatting code. This can result in an uncaught exception that crashes the Node.js process.

The root issue is a corner case failure where the calculation for the error pointer display can produce invalid values, leading to an unhandled exception being thrown rather than gracefully handling the error condition.

Root Cause

The vulnerability stems from improper boundary checking in the error pretty-printer logic. When calculating the number of caret (^) characters to display for error highlighting, the code could compute a value of zero or negative in certain edge cases involving specific column positions. This violates the expected invariants of the String.repeat() method, which requires a non-negative integer, causing an uncaught exception to be thrown.

Attack Vector

An attacker can exploit this vulnerability remotely by submitting specially crafted YAML content to any application that uses the vulnerable eemeli/yaml library for parsing. The attack requires network access but no authentication or user interaction, making it particularly dangerous for web services and APIs that accept YAML input.

The attack flow involves:

Identifying an application endpoint that processes YAML input
Crafting malicious YAML content that triggers the edge case in error handling
Submitting the payload to cause an uncaught exception and application crash

typescript

       let count = 1
       const end = error.linePos[1]
       if (end && end.line === line && end.col > col) {
-        count = Math.min(end.col - col, 80 - ci)
+        count = Math.max(1, Math.min(end.col - col, 80 - ci))
       }
       const pointer = ' '.repeat(ci) + '^'.repeat(count)
       error.message += `:\n\n${lineStr}\n${pointer}\n`

Source: GitHub Commit

Detection Methods for CVE-2023-2251

Indicators of Compromise

Unexpected Node.js process crashes when processing YAML input
Application errors containing stack traces referencing src/errors.ts or error pretty-printer functions
Service unavailability following YAML parsing operations
Log entries showing uncaught exceptions from the yaml package

Detection Strategies

Monitor application logs for uncaught exception errors originating from the eemeli/yaml package
Implement dependency scanning to identify vulnerable versions of the yaml package (prior to 2.0.0-5)
Use Software Composition Analysis (SCA) tools to track vulnerable npm packages in your codebase
Deploy application performance monitoring to detect unusual crash patterns

Monitoring Recommendations

Set up alerting for Node.js process crashes and restarts in production environments
Configure logging to capture full stack traces for uncaught exceptions
Implement rate limiting on endpoints accepting YAML input to mitigate potential DoS attacks
Monitor for unusual patterns of malformed YAML submissions

How to Mitigate CVE-2023-2251

Immediate Actions Required

Update the eemeli/yaml package to version 2.0.0-5 or later immediately
Audit all applications and services using the yaml package to identify vulnerable deployments
Implement input validation and size limits on YAML input before parsing
Consider adding try-catch blocks around YAML parsing operations as a defense-in-depth measure

Patch Information

The vulnerability has been addressed in the GitHub Commit with commit hash 984f5781ffd807e58cad3b5c8da1f940dab75fba. The fix ensures that the count variable used for error pointer display is always at least 1 by using Math.max(1, ...), preventing the edge case that caused the uncaught exception. Users should upgrade to version 2.0.0-5 or later of the yaml package to receive this fix. Additional details are available in the Huntr Vulnerability Bounty report.

Workarounds

Wrap all YAML parsing operations in try-catch blocks to prevent uncaught exceptions from crashing the application
Implement process managers like PM2 or systemd to automatically restart crashed Node.js processes
Add input validation to reject excessively large or malformed YAML before parsing
Consider using alternative YAML parsing libraries if immediate upgrade is not possible

bash

# Update the yaml package to the patched version
npm update yaml@^2.0.0-5

# Or explicitly install the patched version
npm install yaml@2.0.0-5

# Verify the installed version
npm list yaml