CVE-2023-49935

An issue was discovered in SchedMD Slurm 23.02.x and 23.11.x. There is Incorrect Access Control because of a slurmd Message Integrity Bypass. An attacker can reuse root-level authentication tokens during interaction with the slurmd process. This bypasses the RPC message hashes that protect against undesired MUNGE credential reuse. The fixed versions are 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-49935 is rated Moderate Risk (42.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.07%). Review affected assets and schedule remediation.

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-49935

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.86% 0.07% -0.78%
2 2025-11-18 0.07% 0.86% +0.78%
3 2025-11-01 — 0.07% —

Full EPSS history (9 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H 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:L)
A normal user session is enough; they don’t have to be admin.
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]

Weakness enumeration for CVE-2023-49935

OS Trackers for CVE-2023-49935

vendor priority summary link
debian unimportant CVE-2023-49935 unimportant priority: Debian including 1 source packages (slurm-wlm), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2023-49935
gentoo high CVE-2023-49935: 1 GLSA(s) (202409-16), 1 atom(s) (sys-cluster/slurm); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2023-49935
suse medium CVE-2023-49935 severity moderate: SUSE including 232 source package names (libnss_slurm2, libnss_slurm2-23.02.7-1.1, …), 693 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 353, Known Not Affected 340. https://www.suse.com/security/cve/CVE-2023-49935/
ubuntu medium CVE-2023-49935 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, not-affected 5, needs-triage 4, released 1. https://ubuntu.com/security/CVE-2023-49935

Affected software / configurations for CVE-2023-49935

Vendor Product Version Raw CPE
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-49935

cvelogic Threat Intelligence