Microsoft.OpenApi.YamlReader vulnerable to denial of service via YAML alias expansion
microsoft OpenAPI.NET
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft.OpenApi.YamlReader NuGet |
|
|
| Microsoft.OpenApi.Readers NuGet |
|
|
microsoft OpenAPI.NET
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft.OpenApi.YamlReader NuGet |
|
|
| Microsoft.OpenApi.Readers NuGet |
|
|
The OpenAPI.NET SDK contains a useful object model for OpenAPI documents in .NET along with common serializers to extract raw OpenAPI JSON and YAML documents from the model. In Microsoft.OpenApi.Readers versions before 1.6.30 and Microsoft.OpenApi.YamlReader from 2.0.0-preview.11 through 2.11.0 and 3.0.0 through 3.9.0, parsing a YAML OpenAPI document with nested anchors and aliases can consume uncontrolled memory. SharpYaml represents aliases as shared nodes in a small directed acyclic graph, but conversion to independent OpenAPI or System.Text.Json.Nodes.JsonNode trees duplicates every aliased path; without a node-count or nesting-depth limit, N nested anchors referenced k times can require k^N materialized nodes and terminate the process through an out-of-memory condition. The fixed readers bound materialization to 5,000,000 nodes and a nesting depth of 64 by default and report an OpenApiDiagnostic error when a limit is exceeded. This vulnerability is fixed in Microsoft.OpenApi.Readers 1.6.30 and Microsoft.OpenApi.YamlReader 2.12.0 and 3.10.0.
From the CVE record · GitHub_M
Affected OpenAPI.NET readers can consume uncontrolled memory when parsing a YAML OpenAPI document with nested anchors and aliases. An attacker who can supply such a document for parsing could cause the process to terminate from an out-of-memory condition. The input does not specify whether authentication or user interaction is required.
Check applications using NuGet Microsoft.OpenApi.Readers before 1.6.30 or Microsoft.OpenApi.YamlReader from 2.0.0-preview.11 to before 2.12.0, or from 3.0.0 to before 3.10.0.