How severe is CVE-2017-1601?

CVE-2017-1601 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2017-1601 being actively exploited?

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

What products are affected by CVE-2017-1601?

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

How do I fix CVE-2017-1601?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2017-1601 published?

CVE-2017-1601 was published on 2018-05-02 and last updated on 2026-06-17.

CVE-2017-1601

CVE-2017-1601 is a critical-severity vulnerability in Ibm Security Guardium Database Activity Monitor with a CVSS 3.x base score of 9.8. 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-521.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 2% (83rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-521
Affected product: Ibm Security Guardium Database Activity Monitor
Published: 2018-05-02
Last modified: 2026-06-17

Description

IBM Security Guardium 10.0, 10.0.1, and 10.1 through 10.1.4 Database Activity Monitor does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts. IBM X-Force ID: 132624.

Frequently asked questions

What is CVE-2017-1601?: IBM Security Guardium 10.0, 10.0.1, and 10.1 through 10.1.4 Database Activity Monitor does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts. IBM X-Force ID: 132624.
How severe is CVE-2017-1601?: CVE-2017-1601 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-1601 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (83rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-1601?: CVE-2017-1601 primarily affects Ibm Security Guardium Database Activity Monitor. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-1601?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2017-1601 published?: CVE-2017-1601 was published on 2018-05-02 and last updated on 2026-06-17.

References

Affected products (6)

cpe:2.3:a:ibm:security_guardium_database_activity_monitor:10.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:security_guardium_database_activity_monitor:10.0.1:*:*:*:*:*:*:*
cpe:2.3:a:ibm:security_guardium_database_activity_monitor:10.1:*:*:*:*:*:*:*
cpe:2.3:a:ibm:security_guardium_database_activity_monitor:10.1.2:*:*:*:*:*:*:*
cpe:2.3:a:ibm:security_guardium_database_activity_monitor:10.1.3:*:*:*:*:*:*:*
cpe:2.3:a:ibm:security_guardium_database_activity_monitor:10.1.4:*:*:*:*:*:*:*

More vulnerabilities in Ibm Security Guardium Database Activity Monitor

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…
CVE-2016-0237 — Medium (CVSS 5.5): IBM Security Guardium Database Activity Monitor 10 allows local users to obtain sensitive information by reading cached…

All CVEs affecting Ibm Security Guardium Database Activity Monitor →

Other CWE-521 (Weak Password Requirements) vulnerabilities

CVE-2026-25715 — Critical (CVSS 9.8): The web management interface of the device allows the administrator username and password to be set to blank values.…
CVE-2025-53963 — Critical (CVSS 9.8): An issue was discovered on Thermo Fisher Ion Torrent OneTouch 2 INS1005527 devices. They run an SSH server accessible…
CVE-2025-63747 — Critical (CVSS 9.8): QaTraq 6.9.2 ships with administrative account credentials which are enabled in default installations and permit…
CVE-2025-12552 — Critical (CVSS 9.8): Insufficient Password Policy.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.
CVE-2025-11200 — Critical (CVSS 9.8): MLflow Weak Password Requirements Authentication Bypass Vulnerability. This vulnerability allows remote attackers to…
CVE-2025-12364 — Critical (CVSS 9.8): Weak Password Policy.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.

Browse all CWE-521 (Weak Password Requirements) vulnerabilities →