CVE-2017-1198

CVE-2017-1198 is a low-severity vulnerability in Ibm Bigfix Compliance with a CVSS 3.x base score of 3.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-532.

Key facts

Description

IBM BigFix Compliance 1.7 through 1.9.91 (TEMA SUAv1 SCA SCM) stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server logs, referrer header or browser history. IBM X-Force ID: 123673.

Frequently asked questions

What is CVE-2017-1198?
IBM BigFix Compliance 1.7 through 1.9.91 (TEMA SUAv1 SCA SCM) stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server logs, referrer header or browser history. IBM X-Force ID: 123673.
How severe is CVE-2017-1198?
CVE-2017-1198 has a CVSS 3.x base score of 3.7, rated low severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2017-1198 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (64th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-1198?
CVE-2017-1198 affects Ibm Bigfix Compliance. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-1198?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2017-1198 published?
CVE-2017-1198 was published on 2019-02-05 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Ibm Bigfix Compliance

All CVEs affecting Ibm Bigfix Compliance →

Other CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities

Browse all CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities →