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

> Physically proximate attackers can obtain sensitive information by examining the device filesystem due to improper password storage in the Siemens SPCanywhere Android application.

- **Severity:** Low 2.1 (`AV:L/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:** 7 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pc58-v5qw-h9qf

## What is CVE-2015-1598?

CVE-2015-1598 is a low-severity vulnerability in n/a, published on 7 Mar 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Siemens SPCanywhere application for Android does not properly store application passwords, which allows physically proximate attackers to obtain sensitive information by examining the device filesystem.

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

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

It affects 1 product.


Products: Siemens Spcanywhere.

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

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

## Is CVE-2015-1598 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-1597](https://insights.sbomify.com/CVE-2015-1597/): Code injection in n/a (medium 6.8)
- [CVE-2015-1596](https://insights.sbomify.com/CVE-2015-1596/): Weak cryptography in n/a (medium 5.8)
- [CVE-2015-1595](https://insights.sbomify.com/CVE-2015-1595/): Information disclosure in n/a (medium 4.3)
- [CVE-2015-1599](https://insights.sbomify.com/CVE-2015-1599/): Auth bypass in n/a (low 2.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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