Skip to content

Ingress-nginx path sanitization can be bypassed

High severity GitHub Reviewed Published Oct 25, 2023 to the GitHub Advisory Database • Updated Mar 7, 2024

Package

gomod k8s.io/ingress-nginx (Go)

Affected versions

< 1.8.0

Patched versions

1.8.0

Description

Ingress-nginx path sanitization can be bypassed with log_format directive.

References

Published by the National Vulnerability Database Oct 25, 2023
Published to the GitHub Advisory Database Oct 25, 2023
Reviewed Nov 3, 2023
Last updated Mar 7, 2024

Severity

High

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
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
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:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.208%
(59th percentile)

Weaknesses

CVE ID

CVE-2022-4886

GHSA ID

GHSA-gvrm-w2f9-f77q

Source code

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