CVE Tools

CVE-2024-10318

NGINX OpenID Connect Vulnerability

No known exploitation. EPSS puts it in the 31st percentile. Fixed versions are out.

Check it yourself

No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.

Request a scan

Published Updated Sources: CVE.org, NVD, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • F5 NGINX API Connectivity ManagerAffected: ≥ 1.0.0, < 1.9.3Upgrade to: 1.9.3Stated by: CVE record
  • F5 NGINX Ingress ControllerAffected: ≥ 1.0.0, < 3.7.1Upgrade to: 3.7.1Stated by: CVE record
  • F5 NGINX Instance ManagerAffected: ≥ 2.5.0, < 2.17.4Upgrade to: 2.17.4Stated by: CVE record
  • F5 NGINX OpenID ConnectAffected: ≥ fa1ad160e2637d1d583611124478039170d726ab, < 133504f4fd9f72f3e36668f9f2f3d32a86fcb269Upgrade to: 133504f4fd9f72f3e36668f9f2f3d32a86fcb269Stated by: CVE record
  • NGINX Inc. NGINX Instance ManagerAffected: от 2.5.0 до 2.17.4Upgrade to: not statedStated by: BDU

Versions as the sources state them. 3 more products have version data. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS31st
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.4% chance of exploitation activity in the next 30 days, which ranks it in the 31st percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 2 days, from the signal feeds we watch.

  1. Patch availableworkaround available, record updated
  2. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Scored 5.4 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for F5, not every advisory.