kube-apiserver: Server-Side Request Forgery
CVE-2022-3172 is a high-severity server-side request forgery vulnerability in kube-apiserver from Kubernetes, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. Affected kube-apiserver versions: v1.25.0; v1.24.0 through v1.24.4; v1.23.0 through v1.23.10, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 2.46% chance of exploitation within 30 days, higher than 85% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Apiserver to 1.22.14 or 1.23.11 or 1.24.5, whichever matches your release line, or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Kubernetes | kube-apiserver | v1.25.0; v1.24.0 through v1.24.4; v1.23.0 through v1.23.10; v1.22.0 through v1.22.13; v1.21.14 and earlier | Not stated |
| Kubernetes | Apiserver | 1.21.14 and earlier; 1.22.0 up to, but not including, 1.22.14; 1.23.0 up to, but not including, 1.23.11; 1.24.0 up to, but not including, 1.24.5; 1.25.0 | 1.22.14, 1.23.11, 1.24.5 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 5.1 | Medium | CNA (liggitt.net) |
| CVSS 3.1 | 8.2 | High | NVD |
Official description
A security issue was discovered in kube-apiserver that allows an aggregated API server to redirect client traffic to any URL. This could lead to the client performing unexpected actions as well as forwarding the client's API server credentials to third parties.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Server-Side Request Forgery
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
How developers prevent this class of flaw
- If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
- If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/kubernetes/kubernetes/issues/112513Issue Tracking
Other references
Other vulnerabilities in kube-apiserver
- 8.0 High severity
Recent Server-Side Request Forgery vulnerabilities
- 8.8 High severity
- 9.8 Critical severity
- 7.5 High severity
- 7.2 High severity
- 9.8 Critical severity
- 7.2 High severity
Spotted an error? Tell us.