CVE-2024-10318: NGINX OpenID Connect Vulnerability
First published: Wed Nov 06 2024(Updated: )
A session fixation issue was discovered in the NGINX OpenID Connect reference implementation, where a nonce was not checked at login time. This flaw allows an attacker to fix a victim's session to an attacker-controlled account. As a result, although the attacker cannot log in as the victim, they can force the session to associate it with the attacker-controlled account, leading to potential misuse of the victim's session.
Credit: f5sirt@f5.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| PTC ThingWorx Industrial Connectivity | >=1.3.0<1.9.3 | |
| Kubernetes Nginx Ingress Controller | <=1.12.5 | |
| Kubernetes Nginx Ingress Controller | >=2.2.1<=2.4.2 | |
| Kubernetes Nginx Ingress Controller | >=3.0.0<3.7.1 | |
| F5 NGINX Instance Manager | >=2.5.0<2.17.4 | |
| F5 NGINX Plus | <2024-10-24 | |
| NGINX | 3 | |
| F5 NGINX Instance Manager | >=2.5.0<=2.17.3 | 2.17.4 |
| PTC ThingWorx Industrial Connectivity | >=1.3.0<=1.9.2 | 1.9.3 |
| Kubernetes Nginx Ingress Controller | >=3.0.0<=3.7.0 | 3.7.1 |
| Kubernetes Nginx Ingress Controller | >=2.2.1<=2.4.2 | |
| Kubernetes Nginx Ingress Controller | =1.12.5 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-10318?
CVE-2024-10318 is considered a high severity vulnerability due to its potential for session fixation attacks.
How do I fix CVE-2024-10318?
To fix CVE-2024-10318, upgrade to the recommended versions provided in the advisory for affected NGINX products.
Which versions of F5 NGINX products are affected by CVE-2024-10318?
CVE-2024-10318 affects specific versions of F5 NGINX Plus, NGINX Instance Manager, NGINX API Connectivity Manager, and NGINX Ingress Controller as detailed in the advisory.
What is the impact of CVE-2024-10318?
The impact of CVE-2024-10318 allows an attacker to fix a victim's session to an attacker-controlled account, enabling unauthorized actions.
Is there a workaround for CVE-2024-10318?
Currently, there are no recommended workarounds for CVE-2024-10318; upgrading is the primary method of mitigation.
- agent/weakness
- agent/references
- agent/title
- agent/type
- agent/description
- agent/first-publish-date
- agent/severity
- agent/author
- agent/event
- agent/last-modified-date
- collector/mitre-cve
- source/MITRE
- agent/source
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/tags
- agent/softwarecombine
- collector/f5-advisory
- source/F5
- alias/CVE-2024-10318
- vendor/f5
- canonical/ptc thingworx industrial connectivity
- version/ptc thingworx industrial connectivity/1.3.0
- canonical/kubernetes nginx ingress controller
- version/kubernetes nginx ingress controller/1.12.5
- version/kubernetes nginx ingress controller/2.2.1
- version/kubernetes nginx ingress controller/2.4.2
- version/kubernetes nginx ingress controller/3.0.0
- canonical/f5 nginx instance manager
- version/f5 nginx instance manager/2.5.0
- canonical/f5 nginx plus
- canonical/nginx
- version/f5 nginx instance manager/2.17.3
- version/ptc thingworx industrial connectivity/1.9.2
- version/kubernetes nginx ingress controller/3.7.0