# CVE-2018-17555: Information disclosure in n/a

> Remote attackers can obtain sensitive information from ARRIS TG2492LG-NA devices via the /snmpGet oids parameter.

- **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:** 26 Sep 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-866f-hjh4-24xm

## What is CVE-2018-17555?

CVE-2018-17555 is a high-severity vulnerability in n/a, published on 26 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web component on ARRIS TG2492LG-NA 061213 devices allows remote attackers to obtain sensitive information via the /snmpGet oids parameter.

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

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

It affects 1 product.


Products: Commscope Arris Tg2492lg-Na Firmware.

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

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

## Is CVE-2018-17555 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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