# CVE-2017-6531: Missing authorization in n/a

> An unauthenticated attacker can access backup and restore features to read or modify device configuration.

- **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:** 20 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2rjr-rjm7-c6vp

## What is CVE-2017-6531?

CVE-2017-6531 is a critical missing authorization vulnerability in n/a, published on 20 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On Televes COAXDATA GATEWAY 1Gbps devices doc-wifi-hgw_v1.02.0014 4.20, the backup/restore feature lacks access control, related to ReadFile.cgi and LoadCfgFile.

## Which versions are affected by CVE-2017-6531?

It affects 1 product.


Products: Televes Coaxdata Gateway 1gbps Firmware.

## How do I fix CVE-2017-6531?

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

## Is CVE-2017-6531 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-6530](https://insights.sbomify.com/CVE-2017-6530/): Missing authorization in n/a (critical 9.8)
- [CVE-2017-6532](https://insights.sbomify.com/CVE-2017-6532/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6531 and fix it if it is affected.

What it is: CVE-2017-6531 is a critical missing authorization vulnerability in n/a, published on 20 Jul 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-2017-6531 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-2017-6531/ (Markdown: https://insights.sbomify.com/CVE-2017-6531/index.md)
```

## Sources

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

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