GHSA-2H44-X2WX-49F4
Vulnerability from github – Published: 2023-05-22 20:33 – Updated: 2023-06-02 23:57
VLAI?
Summary
Potential HTTP policy bypass when using header rules in Cilium
Details
Impact
This issue only impacts users who:
- Have a HTTP policy that applies to multiple
toEndpointsAND - Have an allow-all rule in place that affects only one of those endpoints
In such cases, a wildcard rule will be appended to the set of HTTP rules, which could cause bypass of HTTP policies.
Patches
This issue has been patched in Cilium 1.11.16, 1.12.9, and 1.13.2.
Workarounds
Rewrite HTTP rules for each endpoint separately. For example, if the initial rule looks like:
egress:
- toEndpoints:
- matchLabels:
k8s:kind: echo
- matchLabels:
k8s:kind: example
toPorts:
- ports:
- port: "8080"
protocol: TCP
rules:
http:
- method: "GET"
It should be rewritten to:
egress:
- toEndpoints:
- matchLabels:
k8s:kind: echo
toPorts:
- ports:
- port: "8080"
protocol: TCP
rules:
http:
- method: "GET"
- toEndpoints:
- matchLabels:
k8s:kind: example
toPorts:
- ports:
- port: "8080"
protocol: TCP
rules:
http:
- method: "GET"
Acknowledgements
The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @jrajahalme for investigating and fixing the issue.
For more information
If you have any questions or comments about this advisory, please reach out on Slack.
As usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: security@cilium.io - first, before disclosing them in any public forums. This is a private mailing list where only members of the Cilium internal security team are subscribed to, and is treated as top priority.
Severity ?
5.3 (Medium)
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/cilium/cilium"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.11.16"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/cilium/cilium"
},
"ranges": [
{
"events": [
{
"introduced": "1.12.0"
},
{
"fixed": "1.12.9"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/cilium/cilium"
},
"ranges": [
{
"events": [
{
"introduced": "1.13.0"
},
{
"fixed": "1.13.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2023-30851"
],
"database_specific": {
"cwe_ids": [
"CWE-693"
],
"github_reviewed": true,
"github_reviewed_at": "2023-05-22T20:33:15Z",
"nvd_published_at": "2023-05-25T18:15:10Z",
"severity": "MODERATE"
},
"details": "### Impact\n\nThis issue only impacts users who:\n\n- Have a HTTP policy that applies to multiple `toEndpoints` AND\n- Have an allow-all rule in place that affects only one of those endpoints\n\nIn such cases, a wildcard rule will be appended to the set of HTTP rules, which could cause bypass of HTTP policies.\n\n### Patches\n\nThis issue has been patched in Cilium 1.11.16, 1.12.9, and 1.13.2.\n\n### Workarounds\n\nRewrite HTTP rules for each endpoint separately. For example, if the initial rule looks like:\n\n```\n egress:\n - toEndpoints:\n - matchLabels:\n k8s:kind: echo\n - matchLabels:\n k8s:kind: example\n toPorts:\n - ports:\n - port: \"8080\"\n protocol: TCP\n rules:\n http:\n - method: \"GET\"\n```\n\nIt should be rewritten to:\n \n```\n egress:\n - toEndpoints:\n - matchLabels:\n k8s:kind: echo\n toPorts:\n - ports:\n - port: \"8080\"\n protocol: TCP\n rules:\n http:\n - method: \"GET\"\n - toEndpoints:\n - matchLabels:\n k8s:kind: example\n toPorts:\n - ports:\n - port: \"8080\"\n protocol: TCP\n rules:\n http:\n - method: \"GET\"\n``` \n\n### Acknowledgements\n\nThe Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @jrajahalme for investigating and fixing the issue.\n\n### For more information\n\nIf you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).\n\nAs usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: [security@cilium.io](mailto:security@cilium.io) - first, before disclosing them in any public forums. This is a private mailing list where only members of the Cilium internal security team are subscribed to, and is treated as top priority.\n",
"id": "GHSA-2h44-x2wx-49f4",
"modified": "2023-06-02T23:57:03Z",
"published": "2023-05-22T20:33:15Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/cilium/cilium/security/advisories/GHSA-2h44-x2wx-49f4"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-30851"
},
{
"type": "PACKAGE",
"url": "https://github.com/cilium/cilium"
},
{
"type": "WEB",
"url": "https://github.com/cilium/cilium/releases/tag/v1.11.16"
},
{
"type": "WEB",
"url": "https://github.com/cilium/cilium/releases/tag/v1.12.9"
},
{
"type": "WEB",
"url": "https://github.com/cilium/cilium/releases/tag/v1.13.2"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Potential HTTP policy bypass when using header rules in Cilium"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…