CVE-2012-1187 Privilege escalation in Bitlbee
Critical 9.8
Published
Updated
Check this codebase for CVE-2012-1187 and fix it if it is affected.
What it is: CVE-2012-1187 is a critical vulnerability in Bitlbee, published on 29 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-1187 in the wild and no public exploit code.
Affected product: Bitlbee. 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-2012-1187/ (Markdown: https://insights.sbomify.com/CVE-2012-1187/index.md)
Bitlbee fails to drop extra group privileges correctly, allowing local attackers to escalate privileges.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2012-1187?
CVE-2012-1187 is a critical vulnerability in Bitlbee, published on 29 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Bitlbee does not drop extra group privileges correctly in unix.c
Weakness: CWE-273
Which versions are affected by CVE-2012-1187?
It affects 1 product.
Products include Bitlbee Bitlbee.
How do I fix CVE-2012-1187?
Apply the vendor's patch.
Is CVE-2012-1187 being exploited?
There is no known exploitation of CVE-2012-1187 in the wild and no public exploit code.
Other vulnerabilities in Bitlbee
- CVE-2016-10188 Use after free in n/a
- CVE-2017-5668 Null dereference in n/a
- CVE-2016-10189 Null dereference in n/a
- CVE-2008-3920 Unspecified vulnerability in BitlBee before 1.2.2 allows remote attackers to "recreate" and "hijack" existing accounts via unspecified vectors.
- CVE-2008-3969 Multiple unspecified vulnerabilities in BitlBee before 1.2.3 allow remote attackers to "overwrite" and "hijack" existing accounts via unknow
Sources
Also known as DEBIAN-CVE-2012-1187, GHSA-h93j-297h-hcxm.