# CVE-2018-13859: Auth bypass in n/a

> Unauthorized remote attackers can bypass authentication by resetting access protection via a specific URL, allowing login without credentials.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pmjj-fc6g-g96r

## What is CVE-2018-13859?

CVE-2018-13859 is a critical authentication bypass vulnerability in n/a, published on 17 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MusicCenter / Trivum Multiroom Setup Tool V8.76 - SNR 8604.26 - C4 Professional before V9.34 build 13381 - 12.07.18, allow unauthorized remote attackers to reset the authentication via the "/xml/system/setAttribute.xml" URL, using the GET request "?id=0&attr=protectAccess&newValue=0" (a successful attack will allow attackers to login without authorization).

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

It affects 1 product.


Products: Trivum C4 Professional Firmware.

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

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

## Is CVE-2018-13859 being exploited?

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

Public exploit code:

- Trivum Multiroom Setup Tool 8.76 - Corss-Site Request Forgery (Admin Bypass) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-13858](https://insights.sbomify.com/CVE-2018-13858/): Missing authorization in n/a (critical 9.8)
- [CVE-2018-13860](https://insights.sbomify.com/CVE-2018-13860/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-13859 is a critical authentication bypass vulnerability in n/a, published on 17 Jul 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-13859 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-13859/ (Markdown: https://insights.sbomify.com/CVE-2018-13859/index.md)
```

## Sources

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

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