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

> Local attackers can read cached web pages from other users' sessions in IBM BigFix Remote Control, exposing sensitive information.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/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:** 30 Nov 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vpqw-qghv-fjg8

## What is CVE-2016-2949?

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

### Official description

IBM BigFix Remote Control before 9.1.3 allows local users to obtain sensitive information by reading cached web pages from a different user's session.

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

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

It affects 1 product.


Products: Ibm Bigfix Remote Control.

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

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

## Is CVE-2016-2949 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-2944](https://insights.sbomify.com/CVE-2016-2944/): Auth bypass in n/a (critical 9.8)
- [CVE-2016-2963](https://insights.sbomify.com/CVE-2016-2963/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-2929](https://insights.sbomify.com/CVE-2016-2929/): Weak cryptography in n/a (high 8.1)
- [CVE-2016-2948](https://insights.sbomify.com/CVE-2016-2948/): Hardcoded credentials in n/a (high 7.8)
- [CVE-2016-2930](https://insights.sbomify.com/CVE-2016-2930/): Auth bypass in BigFix Remote Control (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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