Skip to content

Knative Serving vulnerable to attacker-controlled pod causing denial of service of autoscaler

Moderate severity GitHub Reviewed Published Nov 27, 2023 in knative/serving • Updated Dec 4, 2023

Package

gomod knative.dev/serving (Go)

Affected versions

< 0.39.0

Patched versions

0.39.0

Description

Summary

A vulnerability was fond in Knative Serving that could allow an attacker to crash the Knative Serving autoscaler resulting in a denial of service. The attacker would need to have compromised one pod in the Knative Serving deployment, and with that position they could launch the attack against the autoscaler.
When the autoscaler scrapes the metrics of pods, it sends a request to the /metrics endpoint of each pod and reads the response. The attacker would need to detect the request from the autoscaler to the /metrics endpoint of the pod they had compromised and send a malicious response back to the autoscaler. At this point, the autoscaler would crash. The root cause of the vulnerability was a memory exhaustion issue in the autoscaler that the attacker could trigger with the malicious reponse.

The vulnerability would allow a privilege escalation by the attacker from controlling one point to having negative impact on the entire Knative Serving deployment.

Impact

All users are vulnerable to this; Users that have not had any of their pods compromised are not at risk of this vulnerability.

Mitigation

The vulnerability has been patched in v1.10.5, v1.11.3 and v1.12.0

Credits

The vulnerability was reported by Ada Logics during an ongoing security audit of Knative involving Ada Logics, the Knative maintainers, OSTIF and CNCF.

References

@davidhadas davidhadas published to knative/serving Nov 27, 2023
Published to the GitHub Advisory Database Nov 27, 2023
Reviewed Nov 27, 2023
Published by the National Vulnerability Database Nov 28, 2023
Last updated Dec 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
Low
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:L/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.068%
(31st percentile)

Weaknesses

CVE ID

CVE-2023-48713

GHSA ID

GHSA-qmvj-4qr9-v547

Source code

Credits

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