# CVE-2012-6655: Information disclosure in n/a

> A local attacker can obtain encrypted passwords from the AccountService user change password function, exposing sensitive credential data.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** Yes
- **Published:** 27 Nov 2019
- **Updated:** 6 Aug 2024
- **Also known as:** AZL-44049, DEBIAN-CVE-2012-6655, GHSA-mwwg-gjh6-9grp, UBUNTU-CVE-2012-6655, USN-6687-1

## What is CVE-2012-6655?

CVE-2012-6655 is a low-severity vulnerability in Debian Debian Linux, published on 27 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue exists AccountService 0.6.37 in the user_change_password_authorized_cb() function in user.c which could let a local users obtain encrypted passwords.

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

## Which versions are affected by CVE-2012-6655?

It affects 4 products.


Products: Accountsservice Project Accountsservice, Debian Debian Linux, Opensuse Opensuse, Redhat Enterprise Linux.

## How do I fix CVE-2012-6655?

Apply the vendor's patch.

## Is CVE-2012-6655 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6655 and fix it if it is affected.

What it is: CVE-2012-6655 is a low-severity vulnerability in Debian Debian Linux, published on 27 Nov 2019. 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-2012-6655 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-6655/ (Markdown: https://insights.sbomify.com/CVE-2012-6655/index.md)
```

## Sources

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

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