Skip to content
Fencer Intel
high 7.6

CVE-2023-5044 in the critical feed json

Code injection via nginx.ingress.kubernetes.io/permanent-redirect annotation

published 3y ago modified 2mo ago also GHSA-fp9f-44c2-cw27 , GO-2024-2428 , EUVD-2023-2727

cvss
7.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
53.7%
EPSS 53.7% chance of exploitation in 30 days, percentile 99%
public exploits
0
none known

Summary

Code injection via nginx.ingress.kubernetes.io/permanent-redirect annotation.

Patch / fix

  • go k8s.io/ingress-nginx 1.9.0
  • Kubernetes ingress-nginx 1.9.0

Is CVE-2023-5044 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

53.69% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-14).

CVSS scores

assigned by version score vector
CNA 3.1 7.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 7.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

Affected packages

ecosystem package affected fixed in
go k8s.io/ingress-nginx
<1.9.0
all versions
1.9.0

Affected products

  • Kubernetes ingress-nginx

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-94 Improper Control of Generation of Code
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.