CVE-2022-30535 json
NGINX Ingress Controller vulnerability CVE-2022-30535
published 4y ago modified 4mo ago also BIT-nginx-ingress-controller-2022-30535 , EUVD-2022-52395
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
In versions 2.x before 2.3.0 and all versions of 1.x, An attacker authorized to create or update ingress objects can obtain the secrets available to the NGINX Ingress Controller. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Patch / fix
- bitnami nginx-ingress-controller 2.3.0
- F5 NGINX Ingress Controller 2.3.0
Is CVE-2022-30535 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 FencerExploit prediction
0.71% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | nginx-ingress-controller | >=1.0.0, <2.3.0 |
2.3.0 |
Affected products
- F5 NGINX Ingress Controller
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
support.f5.com
/csp/article/K52125139
vendor-advisory, web
Sources
- CVE List CVE-2022-30535
- NVD CVE-2022-30535
- OSV BIT-nginx-ingress-controller-2022-30535
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.