CVE-2015-1378
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 · uneditedcmdlineopts.clp in grml-debootstrap in Debian 0.54, 0.68.x before 0.68.1, 0.7x before 0.78 is sourced without checking that the local directory is writable by non-root users.
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 · high confidencegrml-debootstrap sources cmdlineopts.clp without verifying that the local directory is writable by non-root users. This allows a local attacker to place a malicious configuration file in a directory where a privileged user runs grml-debootstrap, resulting in arbitrary code execution with root privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 0.54= 0.68= 0.70= 0.71= 0.72= 0.73= 0.74= 0.75= 0.76= 0.77CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
-
Check installed grml-debootstrap versionRun 'grml-debootstrap --version' or check the package version with your package manager (e.g., 'dpkg -l grml-debootstrap' or 'rpm -q grml-debootstrap')Affected if The version displayed matches any of the following: 0.54, 0.68, 0.70, 0.71, 0.72, 0.73, 0.74, 0.75, 0.76, or 0.77
-
Identify directories where grml-debootstrap is executedNote the working directory from which you run grml-debootstrap commands, or inspect any scripts/CI pipelines that invoke itAffected if You run grml-debootstrap from a directory that is writable by non-root users (world-writable or group-writable with a non-root group)
-
Verify directory permissions are insecureRun 'ls -ld <directory>' to check permissions. Look for permissions like 'drwxrwxrwx' (world-writable) or similar group-writable permissions that include non-root usersAffected if The directory shows write permission for 'others' or for a group that non-root users belong to
You are affected if you run an affected version of grml-debootstrap (0.54, 0.68, 0.70-0.77) from a directory that non-root users can write to, allowing them to place a malicious cmdlineopts.clp file for root code execution.
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 dataRestrict directory permissions to prevent non-root users from writing to directories where grml-debootstrap is executed, or modify the code to verify directory writability before sourcing the configuration file.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1378 — 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-2015-1378 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