CVE-2017-1601
UnknownEPSS 2.53%
Last modified
CVE-2017-1601 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.53% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Ibm | Security Guardium Database Activity Monitor | 10.0 |
| Ibm | Security Guardium Database Activity Monitor | 10.0.1 |
| Ibm | Security Guardium Database Activity Monitor | 10.1 |
| Ibm | Security Guardium Database Activity Monitor | 10.1.2 |
| Ibm | Security Guardium Database Activity Monitor | 10.1.3 |
| Ibm | Security Guardium Database Activity Monitor | 10.1.4 |
References
- http://www.ibm.com/support/docview.wss?uid=swg22014230Patch, Vendor Advisory
- http://www.securitytracker.com/id/1040899Third Party Advisory, VDB Entry
- https://exchange.xforce.ibmcloud.com/vulnerabilities/132624VDB Entry, Vendor Advisory
- http://www.ibm.com/support/docview.wss?uid=swg22014230Patch, Vendor Advisory
- http://www.securitytracker.com/id/1040899Third Party Advisory, VDB Entry
- https://exchange.xforce.ibmcloud.com/vulnerabilities/132624VDB Entry, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
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?
Severity scoring for CVE-2017-1601 is pending analysis. The EPSS model estimates a 2.53% probability of exploitation in the next 30 days.
How do I fix CVE-2017-1601?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-16003windows-build-tools is a module for installing C++ Build Too…
- CVE-2017-16005Http-signature is a "Reference implementation of Joyent's HT…
- CVE-2017-16006Remarkable is a markdown parser. In versions 1.6.2 and lower…
- CVE-2017-16007node-jose is a JavaScript implementation of the JSON Object …
- CVE-2017-16008i18next is a language translation framework. Because of how …
- CVE-2017-16009ag-grid is an advanced data grid that is library agnostic. a…6.1
- CVE-2017-16010i18next is a language translation framework. When using the …
- CVE-2017-16011Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultI…
- CVE-2017-16012Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultI…
- CVE-2017-16013hapi is a web and services application framework. When hapi …
- CVE-2017-16014Http-proxy is a proxying library. Because of the way errors …7.5
- CVE-2017-16015Forms is a library for easily creating HTML forms. Versions …
Are you affected by CVE-2017-1601?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST