# CVE-2020-11000: Improper URL validation in GreenBrowser

> Improper URL validation in GreenBrowser allows attackers to bypass access controls by circumventing URL parsing checks used to verify trusted servers.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Apr 2020
- **Updated:** 4 Aug 2024

## What is CVE-2020-11000?

CVE-2020-11000 is a medium-severity vulnerability in luchua-bc GreenBrowser, published on 8 Apr 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

GreenBrowser before version 1.2 has a vulnerability where apps that rely on URL Parsing to verify that a given URL is pointing to a trust server may be susceptible to many different ways to get URL parsing and verification wrong, which allows an attacker to circumvent the access control. This problem has been patched in version 1.2.

Weakness: CWE-939 (Improper Authorization in Handler for Custom URL Scheme)

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

It affects 1 product.


Products: Greenbrowser Project Greenbrowser.

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

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

## Is CVE-2020-11000 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11000 is a medium-severity vulnerability in luchua-bc GreenBrowser, published on 8 Apr 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-11000 in the wild and no public exploit code.

Affected product: luchua-bc GreenBrowser. 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-11000/ (Markdown: https://insights.sbomify.com/CVE-2020-11000/index.md)
```

## Sources

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

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