Skip to content

fieldpath's Paved.SetValue allows growing arrays up to arbitrary sizes in crossplane-runtime

Moderate severity GitHub Reviewed Published Mar 9, 2023 in crossplane/crossplane-runtime • Updated Apr 4, 2023

Package

gomod github.com/crossplane/crossplane-runtime (Go)

Affected versions

>= 0.17.0, < 0.19.2
>= 0.6.0, < 0.16.1

Patched versions

0.19.2
0.16.1

Description

Summary

Fuzz testing on crossplane/crossplane, by Ada Logics and sponsored by the CNCF, identified input to a function in the fieldpath package that can cause an out of memory panic. Applications that use the Paved type's SetValue method with user provided input without proper validation might use excessive amounts of memory and cause an out of memory panic.

Details

In the fieldpath package, the SetValue method of the Paved type sets a value on the inner object according to the provided path, without validating it first. This allows setting values in slices at any specific index and the code will grow the target array up to the required size. The index is currently capped at max uint32 (4294967295) given how indexes are parsed, but that is still an unnecessarily large value.

Workaround

Users can parse and validate the path before passing it to the SetValue method of the Paved type, constraining the index size as deemed appropriate.

Credits

Disclosed by Ada Logics in a fuzzing audit sponsored by CNCF.

References

@turkenh turkenh published to crossplane/crossplane-runtime Mar 9, 2023
Published by the National Vulnerability Database Mar 9, 2023
Published to the GitHub Advisory Database Mar 13, 2023
Reviewed Mar 13, 2023
Last updated Apr 4, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.101%
(43rd percentile)

Weaknesses

CVE ID

CVE-2023-27483

GHSA ID

GHSA-vfvj-3m3g-m532

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.