# CVE-2017-18225: Privilege escalation in n/a

> Local attackers can gain privileges by exploiting insecure file ownership of Jabberd2 binaries, allowing execution as root.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q65j-7f6h-c2fh

## What is CVE-2017-18225?

CVE-2017-18225 is a high-severity vulnerability in n/a, published on 12 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2017-18225?

It affects 1 product.


Products: Jabberd2 Jabberd2.

## How do I fix CVE-2017-18225?

No fix has been published for CVE-2017-18225 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-18225 being exploited?

There is no known exploitation of CVE-2017-18225 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-10807](https://insights.sbomify.com/CVE-2017-10807/): Auth bypass in n/a (critical 9.8)
- [CVE-2015-2058](https://insights.sbomify.com/CVE-2015-2058/): Information disclosure in n/a (medium 6.5)
- [CVE-2017-18226](https://insights.sbomify.com/CVE-2017-18226/): Privilege escalation in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18225 and fix it if it is affected.

What it is: CVE-2017-18225 is a high-severity vulnerability in n/a, published on 12 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-18225 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-18225/ (Markdown: https://insights.sbomify.com/CVE-2017-18225/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-18225
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-18225
- OSV: https://osv.dev/vulnerability/CVE-2017-18225

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-18225/
Summaries are generated and may contain mistakes; the official description above is the record.