# CVE-2018-8770: Information disclosure in n/a

> An attacker can obtain physical path information from Cobub Razor analytics via exposed test files, potentially aiding further attacks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 18 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4788-86m4-464h

## What is CVE-2018-8770?

CVE-2018-8770 is a medium-severity vulnerability in n/a, published on 18 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Physical path Leakage exists in Western Bridge Cobub Razor 0.8.0 via generate.php, controllers/getConfigTest.php, controllers/getUpdateTest.php, controllers/postclientdataTest.php, controllers/posterrorTest.php, controllers/posteventTest.php, controllers/posttagTest.php, controllers/postusinglogTest.php, fixtures/Controller_fixt.php, fixtures/Controller_fixt2.php, fixtures/view_fixt2.php, libs/ipTest.php, or models/commonDbfix.php in tests/.

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

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

It affects 1 product.


Products: Cobub Razor.

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

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

## Is CVE-2018-8770 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-8770 exists.

Public exploit code:

- Cobub Razor 0.8.0 - Physical Path Leakage (exploitdb)
- Cobub Razor 0.8.0 - Information Disclosure (nuclei): http/cves/2018/CVE-2018-8770.yaml

## Other vulnerabilities in n/a

- [CVE-2024-28421](https://insights.sbomify.com/CVE-2024-28421/): SQL injection in n/a (critical 9.8)
- [CVE-2019-10276](https://insights.sbomify.com/CVE-2019-10276/): File upload in n/a (critical 9.8)
- [CVE-2018-7720](https://insights.sbomify.com/CVE-2018-7720/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-7746](https://insights.sbomify.com/CVE-2018-7746/): Cross-site scripting in n/a (high 8.8)
- [CVE-2018-8056](https://insights.sbomify.com/CVE-2018-8056/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-8770 is a medium-severity vulnerability in n/a, published on 18 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-8770 exists.

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

## Sources

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

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