# CVE-2020-8142: Security feature bypass in https://github.com/revive-adserver/revive-adserver

> Attackers with physical access to a logged-in admin interface can bypass password checks to change email or password, leading to account takeover.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x3wg-p2fp-rpxq

## What is CVE-2020-8142?

CVE-2020-8142 is a medium-severity vulnerability in Revive-Adserver Revive Adserver, published on 3 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security restriction bypass vulnerability has been discovered in Revive Adserver version < 5.0.5 by HackerOne user hoangn144. Revive Adserver, like many other applications, requires the logged in user to type the current password in order to change the e-mail address or the password. It was however possible for anyone with access to a Revive Adserver admin user interface to bypass such check and change e-email address or password of the currently logged in user by altering the form payload.The attack requires physical access to the user interface of a logged in user. If the POST payload was altered by turning the “pwold” parameter into an array, Revive Adserver would fetch and authorise the operation even if no password was provided.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Revive-Adserver Revive Adserver.

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

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

## Is CVE-2020-8142 being exploited?

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

## Other vulnerabilities in Revive-Adserver Revive Adserver

- [CVE-2016-9124](https://insights.sbomify.com/CVE-2016-9124/): Security feature bypass in Revive Adserver All versions before 3.2.3 (critical 9.8)
- [CVE-2016-9125](https://insights.sbomify.com/CVE-2016-9125/): Auth bypass in Revive Adserver All versions before 3.2.3 (critical 9.8)
- [CVE-2017-5830](https://insights.sbomify.com/CVE-2017-5830/): Deserialization in n/a (critical 9.8)
- [CVE-2016-9470](https://insights.sbomify.com/CVE-2016-9470/): Other in Revive Adserver All versions before 3.2.5 and 4.0.0 (critical 9.0)
- [CVE-2026-50741](https://insights.sbomify.com/CVE-2026-50741/): Code injection in Adserver (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8142 is a medium-severity vulnerability in Revive-Adserver Revive Adserver, published on 3 Apr 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-8142 in the wild and no public exploit code.

Affected product: Revive-Adserver Revive Adserver. 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-8142/ (Markdown: https://insights.sbomify.com/CVE-2020-8142/index.md)
```

## Sources

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

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