VYPR
Unrated severityNVD Advisory· Published Jan 13, 2020· Updated Aug 5, 2024

CVE-2019-19727

CVE-2019-19727

Description

Slurm slurmdbd.conf is installed with world-readable permissions, exposing database credentials to local users.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Slurm slurmdbd.conf is installed with world-readable permissions, exposing database credentials to local users.

Vulnerability

SchedMD Slurm versions before 18.08.9 and 19.x before 19.05.5 install the slurmdbd.conf configuration file with world-readable permissions (e.g., 0644) instead of the recommended 0600 [1]. This file typically contains the database access password for the SlurmDBD service, making it accessible to any local user on the system.

Exploitation

An attacker with local access to the system where SlurmDBD is installed can read the slurmdbd.conf file without any special privileges. No authentication or user interaction is required beyond having a local user account. The attacker simply reads the file to extract the database credentials.

Impact

Successful exploitation results in disclosure of the database credentials stored in slurmdbd.conf. This can allow the attacker to connect to the Slurm database, potentially leading to unauthorized access, modification, or deletion of job accounting data, user information, and other sensitive records.

Mitigation

The issue is fixed in Slurm versions 18.08.9 and 19.05.5 [1]. Users should upgrade to these or later versions. As a workaround, administrators can manually set the permissions of slurmdbd.conf to 0600 using chmod 0600 /etc/slurm/slurmdbd.conf (or the appropriate path). The SUSE bug report indicates that packaging fixes were applied to ensure correct permissions on installation [1].

AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

19

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

4

News mentions

0

No linked articles in our index yet.