CVE-2023-49933

An issue was discovered in SchedMD Slurm 22.05.x, 23.02.x, and 23.11.x. There is Improper Enforcement of Message Integrity During Transmission in a Communication Channel. This allows attackers to modify RPC traffic in a way that bypasses message hash checks. The fixed versions are 22.05.11, 23.02.7, and 23.11.1.

Published: 2023-12-14 Last update: 2025-11-04 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-49933 is rated Low Risk (36.8/100): CVSS High severity, with low exploitation likelihood (EPSS 0.06%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-49933

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.20% 0.06% -0.14%
2 2025-11-18 0.07% 0.20% +0.13%
3 2025-10-31 — 0.07% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-49933

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2023-49933

OS Trackers for CVE-2023-49933

vendor priority summary link
debian end-of-life CVE-2023-49933 end-of-life priority: Debian including 1 source packages (slurm-wlm), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2023-49933
gentoo high CVE-2023-49933: 1 GLSA(s) (202409-16), 1 atom(s) (sys-cluster/slurm); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2023-49933
suse medium CVE-2023-49933 severity moderate: SUSE including 448 source package names (libnss_slurm2, libnss_slurm2-20.02.7-150200.3.20.1, …), 960 product×package rows across 17 product lines (SUSE Linux Enterprise High Performance Computing 15 SP1-LTSS, SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS, … (17 product lines)): Fixed 879, Known Not Affected 81. https://www.suse.com/security/cve/CVE-2023-49933/
ubuntu medium CVE-2023-49933 medium priority: Ubuntu including 2 source packages (slurm-llnl, slurm-wlm), 24 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 8, ignored 6, needed 5, not-affected 3, needs-triage 2. https://ubuntu.com/security/CVE-2023-49933

Affected software / configurations for CVE-2023-49933

Vendor Product Version Raw CPE
schedmd slurm >= 22.05, < 22.05.12 cpe:2.3:a:schedmd:slurm:*:*:*:*:*:*:*:*
schedmd slurm >= 23.02, < 23.02.7 cpe:2.3:a:schedmd:slurm:*:*:*:*:*:*:*:*
schedmd slurm 23.11 cpe:2.3:a:schedmd:slurm:23.11:-:*:*:*:*:*:*
schedmd slurm 23.11 cpe:2.3:a:schedmd:slurm:23.11:rc1:*:*:*:*:*:*

References for CVE-2023-49933

cvelogic Threat Intelligence