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

> Attackers can discover password hashes by reading files or security logs on Siemens Ruggedcom devices, potentially leading to unauthorized access.

- **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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pg34-hwv9-r5fx

## What is CVE-2015-1357?

CVE-2015-1357 is a medium-severity vulnerability in n/a, published on 2 Feb 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Siemens Ruggedcom WIN51xx devices with firmware before SS4.4.4624.35, WIN52xx devices with firmware before SS4.4.4624.35, WIN70xx devices with firmware before BS4.4.4621.32, and WIN72xx devices with firmware before BS4.4.4621.32 allow context-dependent attackers to discover password hashes by reading (1) files or (2) security logs.

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

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

It affects 1 product.


Products: Siemens Ruggedcom Firmware.

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

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

## Is CVE-2015-1357 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-1448](https://insights.sbomify.com/CVE-2015-1448/): Auth bypass in n/a (critical 10.0)
- [CVE-2015-1449](https://insights.sbomify.com/CVE-2015-1449/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-1357 is a medium-severity vulnerability in n/a, published on 2 Feb 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-1357 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-1357/ (Markdown: https://insights.sbomify.com/CVE-2015-1357/index.md)
```

## Sources

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

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