# CVE-2018-19246: LFI in PHP-Proxy 5.1.0

> Remote attackers can read local files by exploiting hardcoded credentials in the default configuration of PHP-Proxy.

- **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:** 13 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pc5h-m95g-v6rh

## What is CVE-2018-19246?

CVE-2018-19246 is a high-severity path traversal vulnerability in n/a, published on 13 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP-Proxy 5.1.0 allows remote attackers to read local files if the default "pre-installed version" (intended for users who lack shell access to their web server) is used. This occurs because the aeb067ca0aa9a3193dce3a7264c90187 app_key value from the default config.php is in place, and this value can be easily used to calculate the authorization data needed for local file inclusion.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-19246?

2 open source packages ship an affected version, including athlon1600/php-proxy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `athlon1600/php-proxy` | Packagist | All versions to 5.1.0 | None |
| `athlon1600/php-proxy` | Packagist | All versions to 5.1.0 | None |

Products: Php-Proxy Php-Proxy.

## How do I fix CVE-2018-19246?

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

## Is CVE-2018-19246 being exploited?

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

Public exploit code:

- https://github.com/NeoWans/CVE-2018-19246 (github_poc): https://github.com/NeoWans/CVE-2018-19246
- PHP-Proxy 5.1.0 - Local File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-19784](https://insights.sbomify.com/CVE-2018-19784/): Weak Cryptography in PHP-Proxy (high 7.5)
- [CVE-2018-19458](https://insights.sbomify.com/CVE-2018-19458/): Unauthenticated File Read in PHP Proxy (high 7.5)
- [CVE-2018-19785](https://insights.sbomify.com/CVE-2018-19785/): XSS in PHP-Proxy-App through v3.0 (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-19246 and fix it if it is affected.

What it is: CVE-2018-19246 is a high-severity path traversal vulnerability in n/a, published on 13 Nov 2018. 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-2018-19246 in the wild and no public exploit code.

Affected packages and fixed versions:
- athlon1600/php-proxy (Packagist): affected all versions up to 5.1.0; no fix listed
- athlon1600/php-proxy (Packagist): affected all versions up to 5.1.0; no fix listed

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-2018-19246/ (Markdown: https://insights.sbomify.com/CVE-2018-19246/index.md)
```

## Sources

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

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