# CVE-2015-8280: Information disclosure in n/a

> Remote attackers can discover credentials by reading detailed error messages in Samsung SRN-1670D Web Viewer.

- **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:** 15 Jan 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mxw3-p7x5-rc3v

## What is CVE-2015-8280?

CVE-2015-8280 is a high-severity vulnerability in n/a, published on 15 Jan 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Web Viewer 1.0.0.193 on Samsung SRN-1670D devices allows remote attackers to discover credentials by reading detailed error messages.

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

## Which versions are affected by CVE-2015-8280?

It affects 1 product.


Products: Samsung Web Viewer.

## How do I fix CVE-2015-8280?

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

## Is CVE-2015-8280 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-8279](https://insights.sbomify.com/CVE-2015-8279/): Path traversal in n/a (high 8.6)
- [CVE-2015-8281](https://insights.sbomify.com/CVE-2015-8281/): Weak cryptography in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8280 and fix it if it is affected.

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

## Sources

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

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