# CVE-2020-12680: Information disclosure in n/a

> Local attackers can retrieve stored browser credentials from Avira's native messaging executable due to lack of caller verification.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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:** No
- **Published:** 8 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-86wp-7cjf-fh2f

## What is CVE-2020-12680?

CVE-2020-12680 is a medium-severity vulnerability in n/a, published on 8 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Avira Free Antivirus through 15.0.2005.1866 allows local users to discover user credentials. The functions of the executable file Avira.PWM.NativeMessaging.exe are aimed at collecting credentials stored in Chrome, Firefox, Opera, and Edge. The executable does not verify the calling program and thus a request such as fetchChromePasswords or fetchCredentials will succeed. NOTE: some third parties have stated that this is "not a vulnerability.

## Which versions are affected by CVE-2020-12680?

It affects 1 product.


Products: Avira Free Antivirus.

## How do I fix CVE-2020-12680?

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

## Is CVE-2020-12680 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-8961](https://insights.sbomify.com/CVE-2020-8961/): Security feature bypass in n/a (critical 9.8)
- [CVE-2019-18568](https://insights.sbomify.com/CVE-2019-18568/): Privilege escalation in Antivirus Free Antivirus (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12680 and fix it if it is affected.

What it is: CVE-2020-12680 is a medium-severity vulnerability in n/a, published on 8 May 2020. 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-2020-12680 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-2020-12680/ (Markdown: https://insights.sbomify.com/CVE-2020-12680/index.md)
```

## Sources

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

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