CVE-2015-0926
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 · uneditedLabtech before 100.237 on Linux uses world-writable permissions for root-executed scripts, which allows local users to gain privileges by modifying a script file.
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 confidenceLabtech before version 100.237 on Linux stores scripts that are executed with root privileges using world-writable file permissions (likely 777). This allows any local user on the system to modify these scripts and inject arbitrary code that will be executed with root privileges, enabling local privilege escalation.
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<= 55.170CVSS 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
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:S/C:C/I:C/A:C
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 Labtech installation on LinuxSearch for Labtech installation directories, commonly under /usr/local/labtech, /opt/labtech, or check if the 'labtech' service or daemon is present using commands like 'ps aux | grep -i labtech' or 'ls -la /etc/init.d/*labtech*'Affected if Labtech is installed and running on the system
-
Identify Labtech versionCheck the installed version by looking for version files, using package management tools (dpkg, rpm), or examining the Labtech service/daemon information (e.g., 'labtechd --version' or check /opt/labtech/version file if present)Affected if Installed version is lower than 100.237 (versions <= 55.170 are explicitly affected)
-
Find scripts executed with root privilegesExamine the Labtech installation directory for executable scripts, particularly in subdirectories like /scripts, /automation, or /plugins. Look for scripts with shebang lines indicating root execution and check Labtech configuration files that define which scripts are run with elevated privilegesAffected if Labtech scripts intended for root execution exist in the installation directory
-
Check script file permissionsRun 'ls -la' on the identified Labtech scripts and check the permission bits. Specifically examine the owner, group, and other write permissions (the 'w' bit in positions 3, 6, and 9)Affected if Scripts have world-writable permissions (octal 777 or permissions showing 'rwxrwxrwx'), meaning any local user can modify them
A system is affected if Labtech for Linux is installed with a version lower than 100.237 and contains scripts with root execution privileges that have world-writable (777) file permissions, allowing any local user to modify and escalate privileges.
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 dataUpgrade Labtech to version 100.237 or later, which addresses the permission issue. Alternatively, immediately identify and change permissions on affected scripts to restrict write access (e.g., 755 or 700).
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0926 — 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-0926 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