dbcve.org
Nginx Api Connectivity ManagerWeb server / proxy · F5

CVE-2024-10318

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-06
Fix available
A fix is available. Upgrade to 1.9.3 / 2.17.4 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A session fixation vulnerability exists in the NGINX OpenID Connect reference implementation where the nonce parameter is not validated at login time. The nonce, which should be a unique, random value to prevent replay attacks and session hijacking, is not being checked. This allows an attacker to pre-fix a victim's session to an attacker-controlled OIDC account, causing the victim's authenticated session to be associated with the attacker's identity.

MitigationUpdate the NGINX OpenID Connect reference implementation to properly validate the nonce parameter during the OAuth2/OIDC login callback before establishing the authenticated session.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nginx Api Connectivity ManagerWeb server / proxy
Affected:>= 1.3.0, < 1.9.3
Nginx Ingress ControllerWeb server / proxy
Affected:<= 1.12.5>= 2.2.1, <= 2.4.2>= 3.0.0, < 3.7.1
Nginx Instance ManagerWeb server / proxy
Affected:>= 2.5.0, < 2.17.4
Nginx Openid ConnectWeb server / proxy
Affected:< 2024-10-24

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify F5 NGINX OIDC components in use
    Inspect the environment for installed F5 NGINX products that include OpenID Connect functionality. For container environments, check running pods and container images for 'nginx-ingress', 'nginx-instance-manager', or 'nginx-api-connectivity-manager'. For installed software, list installed packages using system package managers or check /var/lib directory for F5 NGINX binaries.
    Affected if Any of the following products are installed: F5 Nginx Api Connectivity Manager, F5 Nginx Ingress Controller, F5 Nginx Instance Manager, or the F5 Nginx OpenID Connect module.
  2. Check product version against affected ranges
    For F5 Nginx Ingress Controller, run 'nginx-ingress-controller --version' or check the image tag. For F5 Nginx Instance Manager, check the installed version via the management interface or package version. For F5 Nginx Api Connectivity Manager, verify the version through the API or management UI. Compare the installed version to: Nginx Api Connectivity Manager < 1.9.3 (and >=1.3.0); Nginx Ingress Controller <=1.12.5, 2.2.1-2.4.2, or 3.0.0-3.7.1; Nginx Instance Manager <2.17.4 (and >=2.5.0); Nginx OpenID Connect versions before 2024-10-24.
    Affected if The installed version falls within any of the affected version ranges.
  3. Verify OIDC authentication is configured
    Inspect NGINX configuration files for OpenID Connect-related directives. Look for 'auth_jwt', 'auth_jwt_key_file', or OIDC module configurations. Check for configuration blocks referencing OAuth2 authorization endpoints, token endpoints, or 'nonce' parameters. In Kubernetes environments, inspect Ingress resources for OIDC annotations such as 'nginx.org/auth-jwt' or similar.
    Affected if OpenID Connect or OAuth2 authentication is configured and active.
  4. Inspect OIDC nonce handling in configuration
    Review the NGINX OIDC configuration files to verify if nonce parameter validation is implemented. Check for code or configuration that validates the 'nonce' parameter during the OAuth2 callback phase. Look for validation logic in the OIDC authorization code flow implementation.
    Affected if The OIDC configuration lacks nonce parameter validation during the login callback phase.

You are affected if you are running any of the affected F5 NGINX products with OIDC authentication enabled and the installed version falls within the affected ranges and nonce validation is not implemented in the OIDC flow.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.3 / 2.17.4 / 3.7.1 or later
Fixed in 1.9.32.17.43.7.1
Interim mitigation

Update the NGINX OpenID Connect reference implementation to properly validate the nonce parameter during the OAuth2/OIDC login callback before establishing the authenticated session.

Recommended fix High confidence

Nginx Api Connectivity Manager >= 1.9.3; Nginx Ingress Controller >= 1.12.6, >= 2.5.0, or >= 3.7.1; Nginx Instance Manager >= 2.17.4; Nginx OpenID Connect >= 2024-10-24

  1. 1. Identify which NGINX product(s) in your environment use the OpenID Connect module (Nginx Api Connectivity Manager, Nginx Ingress Controller, Nginx Instance Manager, or direct Nginx OpenID Connect usage)
  2. 2. For Nginx Api Connectivity Manager: upgrade to version 1.9.3 or later
  3. 3. For Nginx Ingress Controller: upgrade to version 1.12.6, or 2.5.0 or later, or 3.7.1 or later (depending on your major version track)
  4. 4. For Nginx Instance Manager: upgrade to version 2.17.4 or later
  5. 5. For direct Nginx OpenID Connect usage: update to the version released on or after 2024-10-24 which includes proper nonce validation at login time
  6. 6. After upgrade, verify that session fixation protection is functioning by testing that nonce values are properly validated during OpenID Connect authentication flows
Caveat Upgrades may introduce changes to OpenID Connect configuration or behavior; review release notes for your specific product version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nginx Api Connectivity Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10318 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-10318 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data