159 lines
6.9 KiB
JSON
159 lines
6.9 KiB
JSON
{
|
||
"dataType": "CVE_RECORD",
|
||
"dataVersion": "5.2",
|
||
"cveMetadata": {
|
||
"cveId": "CVE-2026-24513",
|
||
"assignerOrgId": "a6081bf6-c852-4425-ad4f-a67919267565",
|
||
"state": "PUBLISHED",
|
||
"assignerShortName": "kubernetes",
|
||
"dateReserved": "2026-01-23T06:54:35.913Z",
|
||
"datePublished": "2026-02-03T22:17:17.315Z",
|
||
"dateUpdated": "2026-02-18T17:29:42.496Z"
|
||
},
|
||
"containers": {
|
||
"cna": {
|
||
"affected": [
|
||
{
|
||
"defaultStatus": "affected",
|
||
"product": "ingress-nginx",
|
||
"repo": "https://github.com/kubernetes/ingress-nginx",
|
||
"vendor": "Kubernetes",
|
||
"versions": [
|
||
{
|
||
"lessThan": "1.13.7",
|
||
"status": "affected",
|
||
"version": "0",
|
||
"versionType": "semver"
|
||
},
|
||
{
|
||
"lessThan": "1.14.3",
|
||
"status": "affected",
|
||
"version": "0",
|
||
"versionType": "semver"
|
||
}
|
||
]
|
||
}
|
||
],
|
||
"datePublic": "2026-02-02T14:00:00.000Z",
|
||
"descriptions": [
|
||
{
|
||
"lang": "en",
|
||
"supportingMedia": [
|
||
{
|
||
"base64": false,
|
||
"type": "text/html",
|
||
"value": "A security issue was discovered in ingress-nginx where the protection afforded by the `auth-url` Ingress annotation may not be effective in the presence of a specific misconfiguration.<br>If the ingress-nginx controller is configured with a default custom-errors configuration that includes HTTP errors 401 or 403, and if the configured default custom-errors backend is defective and fails to respect the X-Code HTTP header, then an Ingress with the `auth-url` annotation may be accessed even when authentication fails.<br>Note that the built-in custom-errors backend works correctly. To trigger this issue requires an administrator to specifically configure ingress-nginx with a broken external component."
|
||
}
|
||
],
|
||
"value": "A security issue was discovered in ingress-nginx where the protection afforded by the `auth-url` Ingress annotation may not be effective in the presence of a specific misconfiguration.\n\nIf the ingress-nginx controller is configured with a default custom-errors configuration that includes HTTP errors 401 or 403, and if the configured default custom-errors backend is defective and fails to respect the X-Code HTTP header, then an Ingress with the `auth-url` annotation may be accessed even when authentication fails.\n\nNote that the built-in custom-errors backend works correctly. To trigger this issue requires an administrator to specifically configure ingress-nginx with a broken external component."
|
||
}
|
||
],
|
||
"impacts": [
|
||
{
|
||
"capecId": "CAPEC-115",
|
||
"descriptions": [
|
||
{
|
||
"lang": "en",
|
||
"value": "CAPEC-115 Authentication Bypass"
|
||
}
|
||
]
|
||
}
|
||
],
|
||
"metrics": [
|
||
{
|
||
"cvssV3_1": {
|
||
"attackComplexity": "HIGH",
|
||
"attackVector": "NETWORK",
|
||
"availabilityImpact": "NONE",
|
||
"baseScore": 3.1,
|
||
"baseSeverity": "LOW",
|
||
"confidentialityImpact": "LOW",
|
||
"integrityImpact": "NONE",
|
||
"privilegesRequired": "LOW",
|
||
"scope": "UNCHANGED",
|
||
"userInteraction": "NONE",
|
||
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N",
|
||
"version": "3.1"
|
||
},
|
||
"format": "CVSS",
|
||
"scenarios": [
|
||
{
|
||
"lang": "en",
|
||
"value": "GENERAL"
|
||
}
|
||
]
|
||
}
|
||
],
|
||
"problemTypes": [
|
||
{
|
||
"descriptions": [
|
||
{
|
||
"cweId": "CWE-754",
|
||
"description": "CWE-754 Improper Check for Unusual or Exceptional Conditions",
|
||
"lang": "en",
|
||
"type": "CWE"
|
||
}
|
||
]
|
||
}
|
||
],
|
||
"providerMetadata": {
|
||
"orgId": "a6081bf6-c852-4425-ad4f-a67919267565",
|
||
"shortName": "kubernetes",
|
||
"dateUpdated": "2026-02-18T17:29:42.496Z"
|
||
},
|
||
"references": [
|
||
{
|
||
"url": "https://github.com/kubernetes/kubernetes/issues/136679"
|
||
}
|
||
],
|
||
"credits": [
|
||
{
|
||
"lang": "en",
|
||
"value": "Aurelia Schittler",
|
||
"type": "finder"
|
||
}
|
||
],
|
||
"source": {
|
||
"discovery": "UNKNOWN"
|
||
},
|
||
"title": "ingress-nginx auth-url protection bypass",
|
||
"x_generator": {
|
||
"engine": "Vulnogram 0.5.0"
|
||
}
|
||
},
|
||
"adp": [
|
||
{
|
||
"metrics": [
|
||
{
|
||
"other": {
|
||
"type": "ssvc",
|
||
"content": {
|
||
"timestamp": "2026-02-04T18:20:39.187137Z",
|
||
"id": "CVE-2026-24513",
|
||
"options": [
|
||
{
|
||
"Exploitation": "none"
|
||
},
|
||
{
|
||
"Automatable": "no"
|
||
},
|
||
{
|
||
"Technical Impact": "partial"
|
||
}
|
||
],
|
||
"role": "CISA Coordinator",
|
||
"version": "2.0.3"
|
||
}
|
||
}
|
||
}
|
||
],
|
||
"title": "CISA ADP Vulnrichment",
|
||
"providerMetadata": {
|
||
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
|
||
"shortName": "CISA-ADP",
|
||
"dateUpdated": "2026-02-04T18:21:14.824Z"
|
||
}
|
||
}
|
||
]
|
||
}
|
||
} |