CVE-2017-14610
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 · uneditedbareos-dir, bareos-fd, and bareos-sd in bareos-core in Bareos 16.2.6 and earlier create a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill `cat /pathname`" command.
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 confidencebareos-dir, bareos-fd, and bareos-sd in bareos-core versions 16.2.6 and earlier create PID files after dropping privileges to a non-root account, creating a TOCTOU race condition. Local users with access to the unprivileged account can modify the PID file before a root script executes 'kill `cat /pathname`', enabling arbitrary process termination.
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<= 16.2.6CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 bareos-core versionRun 'bareos-dir --version' or 'bareos-fd --version' or 'bareos-sd --version' to get the version number. On RPM-based systems, also try 'rpm -qa | grep bareos-core'. On Debian-based systems, try 'dpkg -l | grep bareos'.Affected if The version number returned is 16.2.6 or lower.
-
Locate bareos PID filesSearch for PID files in common locations: 'ls -la /var/run/bareos/' and 'ls -la /run/bareos/'. Also check /var/run/ for files matching 'bareos-*.pid' pattern using 'find /var/run -name "bareos*.pid" -o -name "*bareos*.pid"'.Affected if PID files exist for bareos-dir, bareos-fd, or bareos-sd daemons.
-
Check PID file ownership and permissionsFor each found PID file, run 'ls -la /path/to/bareos-*.pid' to see owner, group, and permissions (e.g., 0644, 0600).Affected if The PID file is owned by a non-root user (like bareos, backup, or daemon) OR has permissions more open than 0600 (such as 0644 or 0666).
-
Verify daemon runs as non-rootRun 'ps aux | grep bareos' to see which user the bareos processes run as. Confirm they run as a non-root service account.Affected if The bareos-dir, bareos-fd, or bareos-sd processes run as a non-root user (such as bareos, backup, or daemon).
A system is affected if bareos-core version 16.2.6 or earlier is installed AND PID files exist that are owned by or accessible to a non-root account, allowing local users to modify the PID file and trigger the race condition.
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 dataEnsure PID files are created before dropping privileges, set restrictive permissions (0600 with root ownership), or use /proc-based PID tracking to eliminate the race condition.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14610 — 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-2017-14610 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