Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-10318: A session fixation issue was discovered in the NGINX OpenID Connect reference implementation, where a nonce wa

32
Routine
MEDIUM 5.4WATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2024-10318 is a medium-severity flaw (CVSS 5.4) affecting nginx api connectivity manager, nginx ingress controller, nginx instance manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score5.4 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance0.4% (top 69%)
CISA exploited listNo
WeaknessCWE-384
Published2024-11-06
Last modified2026-06-17
Publisher (CNA): F5 Networks · Vendor: f5

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

f5 nginx api connectivity manager UPGRADE
Affected: >= 1.3.0 and < 1.9.3
Fixed in: 1.9.3
Safe to downgrade to: a release before 1.3.0
1. Check installed version
apt-cache policy nginx-api-connectivity-manager || rpm -q nginx-api-connectivity-manager || nginx-api-connectivity-manager --version
2. UPGRADE to 1.9.3 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade nginx-api-connectivity-manager
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade nginx-api-connectivity-manager
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.3.0 (Debian / Ubuntu)
apt-cache madison nginx-api-connectivity-manager sudo apt install nginx-api-connectivity-manager=<VERSION_BEFORE_1.3.0> sudo apt-mark hold nginx-api-connectivity-manager
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list nginx-api-connectivity-manager sudo dnf downgrade nginx-api-connectivity-manager-<VERSION_BEFORE_1.3.0> sudo dnf versionlock add nginx-api-connectivity-manager
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
f5 nginx ingress controller UPGRADE
Affected: <= 1.12.5 · >= 2.2.1 and <= 2.4.2 · >= 3.0.0 and < 3.7.1
Fixed in: 3.7.1
Safe to downgrade to: a release before 2.2.1
1. Check installed version
apt-cache policy nginx-ingress-controller || rpm -q nginx-ingress-controller || nginx-ingress-controller --version
2. UPGRADE to 3.7.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade nginx-ingress-controller
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade nginx-ingress-controller
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.2.1 (Debian / Ubuntu)
apt-cache madison nginx-ingress-controller sudo apt install nginx-ingress-controller=<VERSION_BEFORE_2.2.1> sudo apt-mark hold nginx-ingress-controller
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list nginx-ingress-controller sudo dnf downgrade nginx-ingress-controller-<VERSION_BEFORE_2.2.1> sudo dnf versionlock add nginx-ingress-controller
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
f5 nginx instance manager UPGRADE
Affected: >= 2.5.0 and < 2.17.4
Fixed in: 2.17.4
Safe to downgrade to: a release before 2.5.0
1. Check installed version
apt-cache policy nginx-instance-manager || rpm -q nginx-instance-manager || nginx-instance-manager --version
2. UPGRADE to 2.17.4 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade nginx-instance-manager
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade nginx-instance-manager
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.5.0 (Debian / Ubuntu)
apt-cache madison nginx-instance-manager sudo apt install nginx-instance-manager=<VERSION_BEFORE_2.5.0> sudo apt-mark hold nginx-instance-manager
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list nginx-instance-manager sudo dnf downgrade nginx-instance-manager-<VERSION_BEFORE_2.5.0> sudo dnf versionlock add nginx-instance-manager
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
f5 nginx openid connect UPGRADE
Affected: < 2024-10-24
Fixed in: 2024-10-24
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy nginx-openid-connect || rpm -q nginx-openid-connect || nginx-openid-connect --version
2. UPGRADE to 2024-10-24 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade nginx-openid-connect
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade nginx-openid-connect
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-10318?

nginx api connectivity manager: upgrade to 1.9.3; nginx ingress controller: upgrade to 3.7.1; nginx instance manager: upgrade to 2.17.4. Exact commands for each OS are on this page.

Is CVE-2024-10318 being exploited?

CVE-2024-10318 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-10318 affect?

CVE-2024-10318 affects nginx api connectivity manager, nginx ingress controller, nginx instance manager. Severity is medium (CVSS 5.4). 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

How urgent is CVE-2024-10318?

Priority 32/100. On your watchlist

Software pages

nginx vulnerabilities · F5 BIG-IP vulnerabilities

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.