CVE-2024-27763
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 · uneditedXPixelGroup BasicSR through 1.4.2 might locally allow code execution in contrived situations where "scontrol show hostname" is executed in the presence of a crafted SLURM_NODELIST environment variable.
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 · moderate confidenceBasicSR through 1.4.2 contains a command injection vulnerability where executing 'scontrol show hostname' with a crafted SLURM_NODELIST environment variable allows local code execution. The application fails to properly sanitize the environment variable before passing it to the shell when invoking SLURM utilities.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Locate BasicSR installation and versionIdentify where BasicSR is installed (e.g., pip show basicsr, npm show basicsr, or file system search for basicsr directories). Retrieve the version number from the package metadata or version file.Affected if The installed version is 1.4.2 or any version prior to 1.4.2.
-
Verify SLURM environment variables are presentRun 'env | grep -i slurm' or specifically check for the SLURM_NODELIST variable in the environment where BasicSR or its related scripts execute: 'echo $SLURM_NODELIST'.Affected if The SLURM_NODELIST environment variable is set and contains unsanitized user-controlled input (e.g., special shell characters like $, `, or ;).
-
Confirm SLURM utilities are accessibleVerify that the 'scontrol' command is available on the system by running 'which scontrol' or checking its presence in standard SLURM bin directories.Affected if scontrol is executable and accessible to the BasicSR process user.
-
Inspect code for vulnerable scontrol invocationSearch BasicSR source code for patterns calling 'scontrol show hostname' or similar scontrol commands. Use grep or file content search within the BasicSR installation directory.Affected if The code contains an invocation of 'scontrol show hostname' that uses the SLURM_NODELIST environment variable without sanitization.
You are affected if BasicSR version 1.4.2 or earlier is installed, SLURM_NODELIST is set in the execution environment, and the application invokes scontrol show hostname using that variable.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataSanitize or remove the SLURM_NODELIST environment variable before executing scontrol commands, or avoid using scontrol show hostname in BasicSR. If possible, upgrade to a patched version when available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27763 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-27763 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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