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

> Missing HTTPOnly flag in cookie headers allows remote attackers to access sensitive session cookies via script access.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 31 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8v98-rw2q-4wmp

## What is CVE-2017-9492?

CVE-2017-9492 is a high-severity vulnerability in n/a, published on 31 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Comcast firmware on Cisco DPC3939 (firmware version dpc3939-P20-18-v303r20421733-160420a-CMCST); Cisco DPC3939 (firmware version dpc3939-P20-18-v303r20421746-170221a-CMCST); Cisco DPC3939B (firmware version dpc3939b-v303r204217-150321a-CMCST); Cisco DPC3941T (firmware version DPC3941_2.5s3_PROD_sey); and Arris TG1682G (eMTA&DOCSIS version 10.0.132.SIP.PC20.CT, software version TG1682_2.2p7s2_PROD_sey) devices does not include the HTTPOnly flag in a Set-Cookie header for administration applications, which makes it easier for remote attackers to obtain potentially sensitive information via script access to cookies.

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

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

It affects 4 products.


Products: Cisco Dpc3939 Firmware, Cisco Dpc3939b Firmware, Cisco Dpc3941t Firmware, Commscope Arris Tg1682g Firmware.

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

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

## Is CVE-2017-9492 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9479](https://insights.sbomify.com/CVE-2017-9479/): Command injection in n/a (critical 9.8)
- [CVE-2017-9482](https://insights.sbomify.com/CVE-2017-9482/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-9483](https://insights.sbomify.com/CVE-2017-9483/): Command injection in n/a (critical 9.8)
- [CVE-2017-9521](https://insights.sbomify.com/CVE-2017-9521/): Other in n/a (critical 9.8)
- [CVE-2017-9488](https://insights.sbomify.com/CVE-2017-9488/): Hardcoded credentials in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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