CVE-2023-5043: K8s.io/ingress nginx Ingress Nginx Annotation Injection Causes Vulnerability

HIGH
Advisory Identifier: GHSA-5wj4-wffq-3378
CVSS 7.6
CWE-20 CWE-74
Published
Advisory Summary

CVE-2023-5043 is a HIGH (CVSS 7.6) ingress nginx annotation injection causes vulnerability (CWE-20: Improper Input Validation) affecting K8s.io/ingress nginx libraries in the Go ecosystem. The issue involves ingress nginx annotation injection causes arbitrary command execution. Remediation is available by upgrading affected packages to version 1.9.0.

CVE-2023-5043 at a Glance

CVE Identifier CVE-2023-5043
GHSA Identifier GHSA-5wj4-wffq-3378
Severity HIGH
CVSS v3.1 Base Score 7.6
CWE Classification CWE-20: Improper Input Validation
Affected Product K8s.io/ingress nginx
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 7.6

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability Low (A:L)

How to Fix CVE-2023-5043

To remediate this vulnerability, upgrade all affected K8s.io/ingress nginx dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

k8s.io/ingress-nginx fixed: 1.9.0
Upgrade k8s.io/ingress-nginx to 1.9.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for k8s.io/ingress-nginx

How to Check if You Are Affected

To determine whether your application is affected by CVE-2023-5043, inspect your project dependencies for K8s.io/ingress nginx:

inspect dependencies for k8s.io/ingress-nginx

Analyze the terminal output to locate any version of K8s.io/ingress nginx in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.9.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-20: Improper Input Validation, where the product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. In K8s.io/ingress nginx, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Issue Details A security issue was identified in ingress-nginx where the nginx.ingress.kubernetes.io/configuration-snippet annotation on an Ingress object (in the networking.k8s.io or extensions API group) can be used to inject arbitrary commands, and obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access to all secrets in the cluster. This issue has been rated High (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L), and assigned CVE-2023-5043. ### Affected Components and Configurations This bug affects ingress-nginx. If you do not have ingress-nginx installed on your cluster, you are not affected. You can check this by running kubectl get po -n ingress-nginx. If you are running the “chrooted” ingress-nginx controller introduced in v1.2.0 (gcr.io/k8s-staging-ingress-nginx/controller-chroot), command execution is possible but credential extraction is not, so the High severity does not apply. Multi-tenant environments where non-admin users have permissions to create Ingress objects are most affected by this issue. #### Affected Versions <v1.9.0 #### Versions allowing mitigation v1.9.0 ### Mitigation Ingress Administrators should set the --enable-annotation-validation flag to enforce restrictions on the contents of ingress-nginx annotation fields. ### Detection If you find evidence that this vulnerability has been exploited, please contact security@kubernetes.io ### Additional Details See ingress-nginx Issue [#10571](https://github.com/kubernetes/ingress-nginx/issues/10571) for more details. ### Acknowledgements This vulnerability was reported by suanve Thank You, CJ Cullen on behalf of the Kubernetes Security Response Committee

CVE-2023-5043 Affected K8s.io/ingress nginx Versions

1 component(s)
Fixed Versions:
1.9.0
Product / Package Ecosystem Affected Versions Fixed Version
k8s.io/ingress-nginx
Go
< 1.9.0
1.9.0

References

Frequently Asked Questions

What is CVE-2023-5043?
CVE-2023-5043 is a security vulnerability in K8s.io/ingress nginx involving Ingress nginx annotation injection causes arbitrary command execution under CWE-20: Improper Input Validation.
Which K8s.io/ingress nginx versions are affected?
Affected versions include releases prior to 1.9.0 across affected packages: k8s.io/ingress-nginx.
What version fixes CVE-2023-5043?
Upgrading to 1.9.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is k8s.io/ingress-nginx affected?
Yes, k8s.io/ingress-nginx is affected in releases prior to 1.9.0. Upgrade your dependency to 1.9.0 or later.
What is the CVSS score of CVE-2023-5043?
CVE-2023-5043 has a CVSS v3.1 base score of 7.6 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L.
What CWE is associated with CVE-2023-5043?
CVE-2023-5043 is classified under CWE-20: Improper Input Validation (The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.).
How can I check Go dependencies for CVE-2023-5043?
Run the dependency tree command: 'inspect dependencies for k8s.io/ingress-nginx'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5wj4-wffq-3378",
  "modified" : "2025-02-13T19:18:20Z",
  "published" : "2023-10-25T21:30:33Z",
  "aliases" : [ "CVE-2023-5043" ],
  "summary" : "Ingress nginx annotation injection causes arbitrary command execution",
  "details" : "### Issue Details\nA security issue was identified in ingress-nginx where the nginx.ingress.kubernetes.io/configuration-snippet annotation on an Ingress object (in the networking.k8s.io or extensions API group) can be used to inject arbitrary commands, and obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access to all secrets in the cluster.\n\nThis issue has been rated High (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L), and assigned CVE-2023-5043.\n\n### Affected Components and Configurations\nThis bug affects ingress-nginx. If you do not have ingress-nginx installed on your cluster, you are not affected. You can check this by running kubectl get po -n ingress-nginx.\n\nIf you are running the “chrooted” ingress-nginx controller introduced in v1.2.0 (gcr.io/k8s-staging-ingress-nginx/controller-chroot), command execution is possible but credential extraction is not, so the High severity does not apply.\n\nMulti-tenant environments where non-admin users have permissions to create Ingress objects are most affected by this issue.\n\n#### Affected Versions\n<v1.9.0\n#### Versions allowing mitigation\nv1.9.0\n### Mitigation\nIngress Administrators should set the --enable-annotation-validation flag to enforce restrictions on the contents of ingress-nginx annotation fields.\n\n### Detection\nIf you find evidence that this vulnerability has been exploited, please contact security@kubernetes.io\n\n### Additional Details\nSee ingress-nginx Issue [#10571](https://github.com/kubernetes/ingress-nginx/issues/10571) for more details.\n\n### Acknowledgements\nThis vulnerability was reported by suanve\n\nThank You,\nCJ Cullen on behalf of the Kubernetes Security Response Committee",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "k8s.io/ingress-nginx"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.9.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-5043"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/kubernetes/ingress-nginx/issues/10571"
  }, {
    "type" : "WEB",
    "url" : "https://groups.google.com/g/kubernetes-security-announce/c/pVsXsOpxYZo"
  }, {
    "type" : "WEB",
    "url" : "https://security.netapp.com/advisory/ntap-20240307-0012"
  }, {
    "type" : "WEB",
    "url" : "http://www.openwall.com/lists/oss-security/2023/10/25/4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-20", "CWE-74" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-11-03T19:13:55Z",
    "nvd_published_at" : "2023-10-25T20:15:18Z"
  }
}