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

> Unauthenticated attackers can obtain sensitive device information from Buffalo TS5600D1206 NAS devices via an incorrect access control flaw.

- **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:** 26 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rvj5-6vm4-x5gx

## What is CVE-2018-13319?

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

### Official description

Incorrect access control in get_portal_info in Buffalo TS5600D1206 version 3.61-0.10 allows attackers to determine sensitive device information via an unauthenticated POST request.

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

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

It affects 1 product.


Products: Buffalo Ts5600d1206 Firmware.

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

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

## Is CVE-2018-13319 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-13324](https://insights.sbomify.com/CVE-2018-13324/): Auth bypass in n/a (critical 9.8)
- [CVE-2018-13321](https://insights.sbomify.com/CVE-2018-13321/): Missing authorization in n/a (high 8.8)
- [CVE-2018-13318](https://insights.sbomify.com/CVE-2018-13318/): Command injection in n/a (high 7.2)
- [CVE-2018-13320](https://insights.sbomify.com/CVE-2018-13320/): Command injection in n/a (high 7.2)
- [CVE-2018-13322](https://insights.sbomify.com/CVE-2018-13322/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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