# CVE-2018-12301: Server-side request forgery in n/a

> Attackers can exploit unvalidated URLs in the Download Manager to access the loopback interface, potentially reading internal data or bypassing security controls.

- **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 May 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wh64-24j9-gm4r

## What is CVE-2018-12301?

CVE-2018-12301 is a high-severity server-side request forgery vulnerability in n/a, published on 13 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unvalidated URL in Download Manager in Seagate NAS OS version 4.3.15.1 allows attackers to access the loopback interface via a Download URL of 127.0.0.1 or localhost.

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

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

It affects 1 product.


Products: Seagate Nas Os.

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

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

## Is CVE-2018-12301 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-12295](https://insights.sbomify.com/CVE-2018-12295/): SQL injection in n/a (critical 9.8)
- [CVE-2018-12296](https://insights.sbomify.com/CVE-2018-12296/): Missing authorization in n/a (high 7.5)
- [CVE-2018-12298](https://insights.sbomify.com/CVE-2018-12298/): Path traversal in n/a (high 7.5)
- [CVE-2018-12297](https://insights.sbomify.com/CVE-2018-12297/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2018-12300](https://insights.sbomify.com/CVE-2018-12300/): Open redirect in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-12301 is a high-severity server-side request forgery vulnerability in n/a, published on 13 May 2019. 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-12301 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-2018-12301/ (Markdown: https://insights.sbomify.com/CVE-2018-12301/index.md)
```

## Sources

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

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