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

> Remote attackers can obtain sensitive network connection information from Janitza UMG devices by sending requests to specific UDP ports.

- **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:** 28 Oct 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2fxp-6j83-m9h5

## What is CVE-2015-3969?

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

### Official description

Janitza UMG 508, 509, 511, 604, and 605 devices allow remote attackers to obtain sensitive network-connection information via a request to UDP port (1) 1234 or (2) 1235.

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

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

It affects 5 products.


Products: Janitza Umg 508, Janitza Umg 509, Janitza Umg 511, Janitza Umg 604, Janitza Umg 605.

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

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

## Is CVE-2015-3969 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-3972](https://insights.sbomify.com/CVE-2015-3972/): Weak cryptography in n/a (critical 10.0)
- [CVE-2015-3968](https://insights.sbomify.com/CVE-2015-3968/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2015-3971](https://insights.sbomify.com/CVE-2015-3971/): Missing authorization in n/a (high 7.5)
- [CVE-2015-3967](https://insights.sbomify.com/CVE-2015-3967/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2015-3973](https://insights.sbomify.com/CVE-2015-3973/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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