# CVE-2020-27192: Security feature bypass in n/a

> A local attacker can inject code into ForkLift due to disabled library validation, enabling privilege escalation via the helper tool.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 17 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f92h-24fv-q8vj

## What is CVE-2020-27192?

CVE-2020-27192 is a high-severity vulnerability in n/a, published on 17 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

BinaryNights ForkLift 3.4 was compiled with the com.apple.security.cs.disable-library-validation flag enabled which allowed a local attacker to inject code into ForkLift. This would allow the attacker to run malicious code with escalated privileges through ForkLift's helper tool.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Binarynights Forklift.

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

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

## Is CVE-2020-27192 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15349](https://insights.sbomify.com/CVE-2020-15349/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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