# CVE-2016-10042: Missing authorization in n/a

> Unauthenticated attackers can reconfigure static routing tables on Arcadyan Star devices, causing denial of service and information disclosure.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 29 Jun 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hgvm-p3qr-6gxx

## What is CVE-2016-10042?

CVE-2016-10042 is a high-severity missing authorization vulnerability in n/a, published on 29 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authorization Bypass in the Web interface of Arcadyan SLT-00 Star* (aka Swisscom Internet-Box) devices before R7.7 allows unauthorized reconfiguration of the static routing table via an unauthenticated HTTP request, leading to denial of service and information disclosure.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2016-10042?

It affects 1 product.


Products: Arcadyan Swisscom Internet-Box Firmware.

## How do I fix CVE-2016-10042?

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

## Is CVE-2016-10042 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10042 and fix it if it is affected.

What it is: CVE-2016-10042 is a high-severity missing authorization vulnerability in n/a, published on 29 Jun 2017. 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-2016-10042 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-2016-10042/ (Markdown: https://insights.sbomify.com/CVE-2016-10042/index.md)
```

## Sources

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

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