# CVE-2019-6481: Auth bypass in n/a

> Attackers can bypass second-factor authentication in the Abine Blur Chrome plugin by accessing a hidden developer menu via right-click.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qf72-pp6j-rxg5

## What is CVE-2019-6481?

CVE-2019-6481 is a high-severity authentication bypass vulnerability in n/a, published on 29 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Abine Blur 7.8.2431 allows remote attackers to conduct "Second-Factor Auth Bypass" attacks by using the "Perform a right-click operation to access a forgotten dev menu to insert user passwords that otherwise would require the user to accept a second-factor request in a mobile app." approach, related to a "Multifactor Auth Bypass, Full Disk Encryption Bypass" issue affecting the Affected Chrome Plugin component.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-6481?

It affects 1 product.


Products: Abine Blur.

## How do I fix CVE-2019-6481?

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

## Is CVE-2019-6481 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-7213](https://insights.sbomify.com/CVE-2018-7213/): Security feature bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6481 and fix it if it is affected.

What it is: CVE-2019-6481 is a high-severity authentication bypass vulnerability in n/a, published on 29 Mar 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-2019-6481 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-2019-6481/ (Markdown: https://insights.sbomify.com/CVE-2019-6481/index.md)
```

## Sources

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

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