# CVE-2016-5849: Information disclosure in n/a

> Local attackers can access sensitive configuration data in Siemens SICAM PAS by stopping the database, requiring vendor patches.

- **Severity:** Low 2.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jul 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-47qc-ch82-95fv

## What is CVE-2016-5849?

CVE-2016-5849 is a low-severity vulnerability in n/a, published on 4 Jul 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Siemens SICAM PAS through 8.07 allows local users to obtain sensitive configuration information by leveraging database stoppage.

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

## Which versions are affected by CVE-2016-5849?

It affects 1 product.


Products: Siemens Sicam Pas\/Pqs.

## How do I fix CVE-2016-5849?

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

## Is CVE-2016-5849 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-43724](https://insights.sbomify.com/CVE-2022-43724/): Hardcoded credentials in SICAM PAS/PQS (critical 9.8)
- [CVE-2016-8567](https://insights.sbomify.com/CVE-2016-8567/): Hardcoded credentials in Siemens SICAM PAS before 8.00 (critical 9.8)
- [CVE-2016-9157](https://insights.sbomify.com/CVE-2016-9157/): Denial of service in Siemens SICAM PAS through V8.08 (critical 9.8)
- [CVE-2023-45205](https://insights.sbomify.com/CVE-2023-45205/): Privilege escalation in SICAM PAS/PQS (high 7.8)
- [CVE-2022-43722](https://insights.sbomify.com/CVE-2022-43722/): Code injection in SICAM PAS/PQS (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5849 and fix it if it is affected.

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

## Sources

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

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