CVE-2019-13657
CVE-2019-13657 Vulnerability Analysis & Exploit Intelligence
CA Performance Management 3.5.x, 3.6.x before 3.6.9, and 3.7.x before 3.7.4 have a default credential vulnerability that can allow a remote attacker to execute arbitrary commands and compromise system security.
Published Updated Sources: cvelistV5, ca
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
3%
chance of exploitation in 30 days
CVSS base
9.8
CRITICAL
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | CRITICAL | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-798
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1552.001Unsecured Credentials: Credentials in files
- T1078.001Valid Accounts: Default Accounts
References
5 on the record
- seclists.org/bugtraq/2019/Oct/26
mailing-list, x_refsource_BUGTRAQ
- packetstormsecurity.com/files/154904/CA-Performance-Management-Arbitary-Command-Execution.html
x_refsource_MISC
- techdocs.broadcom.com/us/product-content/recommended-reading/security-notices/ca-20191015-01-security-notice-for-ca-performance-management.html
x_refsource_CONFIRM
- packetstormsecurity.com/files/154904/CA-Performance-Management-Arbitrary-Command-Execution.html
x_refsource_MISC
- seclists.org/fulldisclosure/2019/Oct/37
mailing-list, x_refsource_FULLDISC
Elsewhere on this site
- ca technologies a broadcomevery CVE for this vendor
- CWE-798other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.