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

> Remote attackers can sniff network traffic to obtain cleartext credentials from Sauter moduWeb Vision 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:** 6 Feb 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-42fv-jxfg-2qh3

## What is CVE-2015-7915?

CVE-2015-7915 is a critical vulnerability in n/a, published on 6 Feb 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sauter EY-WS505F0x0 moduWeb Vision before 1.6.0 sends cleartext credentials, which allows remote attackers to obtain sensitive information by sniffing the network.

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

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

It affects 1 product.


Products: Sauter Moduweb Vision.

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

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

## Is CVE-2015-7915 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-7914](https://insights.sbomify.com/CVE-2015-7914/): Sauter EY-WS505F0x0 moduWeb Vision before 1.6.0 allows remote attackers to bypass authentication by leveraging knowledge of a password hash (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-7915 is a critical vulnerability in n/a, published on 6 Feb 2016. 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-7915 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-7915/ (Markdown: https://insights.sbomify.com/CVE-2015-7915/index.md)
```

## Sources

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

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