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

> Unauthenticated attackers can download sensitive PHP configuration files from the Peplink Balance Web Admin interface.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 7 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-873q-6mjj-g9m5

## What is CVE-2020-24246?

CVE-2020-24246 is a high-severity vulnerability in n/a, published on 7 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Peplink Balance before 8.1.0rc1 allows an unauthenticated attacker to download PHP configuration files (/filemanager/php/connector.php) from Web Admin.

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

It affects 55 products.


Products: Peplink Balance 1350 Firmware, Peplink Balance 20 Firmware, Peplink Balance 20x Firmware, Peplink Balance 210 Firmware, Peplink Balance 2500 Firmware, Peplink Balance 305 Firmware, Peplink Balance 30 Firmware, Peplink Balance 30 Lte Firmware, Peplink Balance 30 Pro Firmware, Peplink Balance 310 Firmware, Peplink Balance 310x Firmware, Peplink Balance 380 Firmware, Peplink Balance 50 Firmware, Peplink Balance 580 Firmware, Peplink Balance 710 Firmware, Peplink Balance One Firmware, Peplink Balance Two Firmware, Peplink Epx Firmware, Peplink Fusionhub Firmware, Peplink Max 700 Firmware and 35 more.

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

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

## Is CVE-2020-24246 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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