CVE-2017-18225
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 · uneditedThe Gentoo net-im/jabberd2 package through 2.6.1 installs jabberd, jabberd2-c2s, jabberd2-router, jabberd2-s2s, and jabberd2-sm in /usr/bin owned by the jabber account, which might allow local users to gain privileges by leveraging access to this account and then waiting for root to execute one of these programs.
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 confidenceThe Gentoo net-im/jabberd2 package (versions through 2.6.1) installs its binaries (jabberd, jabberd2-c2s, jabberd2-router, jabberd2-s2s, and jabberd2-sm) in /usr/bin with ownership by the jabber user account rather than root. This allows local users who have access to the jabber account to potentially escalate privileges by waiting for root or privileged users to execute these binaries.
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<= 2.6.1CVSS 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.
-
Verify jabberd2 package installationRun `equery jabberd2` or check if any of the jabberd2 binaries exist in /usr/bin using `ls -la /usr/bin/jabberd*`Affected if jabberd2 binaries are found in /usr/bin
-
Check ownership of jabberd binaryRun `ls -la /usr/bin/jabberd` and examine the owner and group columnsAffected if The owner or group is 'jabber' instead of 'root'
-
Check ownership of jabberd2-c2s binaryRun `ls -la /usr/bin/jabberd2-c2s` and examine the owner and group columnsAffected if The owner or group is 'jabber' instead of 'root'
-
Check ownership of jabberd2-router binaryRun `ls -la /usr/bin/jabberd2-router` and examine the owner and group columnsAffected if The owner or group is 'jabber' instead of 'root'
-
Check ownership of jabberd2-s2s binaryRun `ls -la /usr/bin/jabberd2-s2s` and examine the owner and group columnsAffected if The owner or group is 'jabber' instead of 'root'
-
Check ownership of jabberd2-sm binaryRun `ls -la /usr/bin/jabberd2-sm` and examine the owner and group columnsAffected if The owner or group is 'jabber' instead of 'root'
If any jabberd2 binary in /usr/bin is owned by the jabber user or group instead of root, the environment is affected by this vulnerability.
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 dataChange ownership of the jabberd2 binaries in /usr/bin from jabber:jabber to root:root and set permissions to 755 (or appropriate executable permissions), then verify jabberd2 functionality continues normally.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18225 — 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-18225 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