How severe is CVE-2016-0240?

CVE-2016-0240 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-2016-0240 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (60th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2016-0240?

CVE-2016-0240 primarily affects Ibm Security Guardium Database Activity Monitor. In total, 7 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2016-0240?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2016-0240 published?

CVE-2016-0240 was published on 2016-10-22 and last updated on 2026-06-17.

CVE-2016-0240

CVE-2016-0240 is a low-severity vulnerability in Ibm Security Guardium Database Activity Monitor 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-254.

Key facts

Severity: Low (CVSS 3.x base score 3.7)
CVSS v2: 4.3
EPSS exploit prediction: 1% (60th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-254
Affected product: Ibm Security Guardium Database Activity Monitor
Published: 2016-10-22
Last modified: 2026-06-17

Description

IBM Security Guardium Database Activity Monitor 8.2 before p310, 9.x through 9.5 before p700, and 10.x through 10.1 before p100 does not enable the HSTS protection mechanism, which makes it easier for remote attackers to obtain sensitive information by leveraging use of HTTP.

Frequently asked questions

What is CVE-2016-0240?: IBM Security Guardium Database Activity Monitor 8.2 before p310, 9.x through 9.5 before p700, and 10.x through 10.1 before p100 does not enable the HSTS protection mechanism, which makes it easier for remote attackers to obtain sensitive information by leveraging use of HTTP.
How severe is CVE-2016-0240?: CVE-2016-0240 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-2016-0240 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (60th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-0240?: CVE-2016-0240 primarily affects Ibm Security Guardium Database Activity Monitor. In total, 7 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2016-0240?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2016-0240 published?: CVE-2016-0240 was published on 2016-10-22 and last updated on 2026-06-17.

References

Affected products (7)

cpe:2.3:a:ibm:security_guardium_database_activity_monitor:8.2:*:*:*:*:*:*:*
cpe:2.3:a:ibm:security_guardium_database_activity_monitor:9.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:security_guardium_database_activity_monitor:9.1:*:*:*:*:*:*:*
cpe:2.3:a:ibm:security_guardium_database_activity_monitor:9.5:*:*:*:*:*:*:*
cpe:2.3:a:ibm:security_guardium_database_activity_monitor:10.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:security_guardium_database_activity_monitor:10.1:*:*:*:*:*:*:*
cpe:2.3:a:ibm:security_guardium_database_activity_monitor:10.01:*:*:*:*:*:*:*

More vulnerabilities in Ibm Security Guardium Database Activity Monitor

CVE-2017-1601 — Critical (CVSS 9.8): IBM Security Guardium 10.0, 10.0.1, and 10.1 through 10.1.4 Database Activity Monitor does not require that users…
CVE-2016-0241 — High (CVSS 8.8): IBM Security Guardium Database Activity Monitor 8.2 before p310, 9.x through 9.5 before p700, and 10.x through 10.1…
CVE-2016-0239 — High (CVSS 8.8): IBM Security Guardium Database Activity Monitor 9.x through 9.5 before p700 and 10.x through 10.0.1 before p100 allows…
CVE-2016-0236 — High (CVSS 8.8): IBM Security Guardium Database Activity Monitor 8.2 before p310, 9.x through 9.5 before p700, and 10.x through 10.1…
CVE-2016-0235 — High (CVSS 8.2): IBM Security Guardium Database Activity Monitor 10 allows local users to have unspecified impact by leveraging…
CVE-2016-0328 — High (CVSS 7.8): IBM Security Guardium Database Activity Monitor 8.2 before p310, 9.x through 9.5 before p700, and 10.x through 10.1…

All CVEs affecting Ibm Security Guardium Database Activity Monitor →

Other CWE-254 vulnerabilities

CVE-2016-5788 — Critical (CVSS 10.0): General Electric (GE) Bently Nevada 3500/22M USB with firmware before 5.0 and Bently Nevada 3500/22M Serial have open…
CVE-2015-3972 — Critical (CVSS 10.0): The web interface on Janitza UMG 508, 509, 511, 604, and 605 devices supports only short PIN values for authentication,…
CVE-2015-1158 — Critical (CVSS 10.0): The add_job function in scheduler/ipp.c in cupsd in CUPS before 2.0.3 performs incorrect free operations for…
CVE-2019-15149 — Critical (CVSS 9.8): core.py in Mitogen before 0.2.8 has a typo that drops the unidirectional-routing protection mechanism in the case of a…
CVE-2017-8227 — Critical (CVSS 9.8): Amcrest IPM-721S V2.420.AC00.16.R.20160909 devices have a timeout policy to wait for 5 minutes in case 30 incorrect…
CVE-2016-9568 — Critical (CVSS 9.8): A security design issue can allow an unprivileged user to interact with the Carbon Black Sensor and perform…

Browse all CWE-254 vulnerabilities →