# CVE-2017-1177: Information disclosure in BigFix Compliance

> Unauthorized users can access sensitive information in IBM BigFix Compliance, potentially facilitating further system attacks.

- **Severity:** Medium 5.3 (`CVSS:3.0/A:N/AC:L/AV:N/C:L/I:N/PR:N/S:U/UI:N/E:U/RC:C/RL:O`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7qvr-7mv3-w74v

## What is CVE-2017-1177?

CVE-2017-1177 is a medium-severity vulnerability in IBM BigFix Compliance, published on 5 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM BigFix Compliance 1.7 through 1.9.91 discloses sensitive information to unauthorized users. The information can be used to mount further attacks on the system. IBM X-Force ID: 123429.

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

## Which versions are affected by CVE-2017-1177?

It affects 1 product.


Products: Ibm Bigfix Compliance.

## How do I fix CVE-2017-1177?

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

## Is CVE-2017-1177 being exploited?

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

## Other vulnerabilities in IBM BigFix Compliance

- [CVE-2017-1202](https://insights.sbomify.com/CVE-2017-1202/): Cross-site scripting in BigFix Compliance (medium 5.4)
- [CVE-2017-1198](https://insights.sbomify.com/CVE-2017-1198/): Information disclosure in BigFix Compliance (low 3.7)
- [CVE-2017-1200](https://insights.sbomify.com/CVE-2017-1200/): Security feature bypass in BigFix Compliance (low 3.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1177 and fix it if it is affected.

What it is: CVE-2017-1177 is a medium-severity vulnerability in IBM BigFix Compliance, published on 5 Feb 2019. 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-2017-1177 in the wild and no public exploit code.

Affected product: IBM BigFix Compliance. 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-2017-1177/ (Markdown: https://insights.sbomify.com/CVE-2017-1177/index.md)
```

## Sources

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

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