# CVE-2017-6094: Information disclosure in n/a

> Attackers can forge authentication tokens to retrieve sensitive configuration data, including VoIP credentials, from other subscribers' devices.

- **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 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wgvq-q9gr-9f24

## What is CVE-2017-6094?

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

### Official description

CPEs used by subscribers on the access network receive their individual configuration settings from a central GAPS instance. A CPE identifies itself by the MAC address of its WAN interface and a certain "chk" value (48bit) derived from the MAC. The algorithm used to compute the "chk" was disclosed by reverse engineering the CPE's firmware. As a result, it is possible to forge valid "chk" values for any given MAC address and therefore receive the configuration settings of other subscribers' CPEs. The configuration settings often contain sensitive values, for example credentials (username/password) for VoIP services. This issue affects Genexis B.V. GAPS up to 7.2.

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

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

It affects 1 product.


Products: Genexis Gaps.

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

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

## Is CVE-2017-6094 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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