# CVE-2015-1892: Information disclosure in n/a

> Remote attackers can cause denial of service or obtain sensitive information via unicast mDNS queries in IBM Security Access Manager.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** 1 Apr 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wr75-h66j-9v32

## What is CVE-2015-1892?

CVE-2015-1892 is a medium-severity vulnerability in n/a, published on 1 Apr 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Multicast DNS (mDNS) responder in IBM Security Access Manager for Web 7.x before 7.0.0 FP12 and 8.x before 8.0.1 FP1 inadvertently responds to unicast queries with source addresses that are not link-local, which allows remote attackers to cause a denial of service (traffic amplification) or obtain potentially sensitive information via port-5353 UDP packets.

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

## Which versions are affected by CVE-2015-1892?

It affects 2 products.


Products: Ibm Security Access Manager for Web 7.0 Firmware, Ibm Security Access Manager for Web 8.0 Firmware.

## How do I fix CVE-2015-1892?

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

## Is CVE-2015-1892 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-4809](https://insights.sbomify.com/CVE-2014-4809/): Denial of service in n/a (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1892 and fix it if it is affected.

What it is: CVE-2015-1892 is a medium-severity vulnerability in n/a, published on 1 Apr 2015. 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-2015-1892 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-2015-1892/ (Markdown: https://insights.sbomify.com/CVE-2015-1892/index.md)
```

## Sources

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

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