CVE-2019-13657 json
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…
published 7y ago modified 4mo ago also EUVD-2019-5077
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- broadcom ca_performance_management 3.6.9, 3.7.4
Is CVE-2019-13657 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.50% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Affected products
- CA Technologies, A Broadcom Company CA Performance Management
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
techdocs.broadcom.com
/us/product-content/recommended-reading/security-notices/ca-20191015-01-security-notice-for-ca-performance-man
vendor-advisory
-
seclists.org
/bugtraq/2019/Oct/26
mailing-list, issue-tracking, third-party-advisory
-
packetstormsecurity.com
/files/154904/CA-Performance-Management-Arbitary-Command-Execution.html
third-party-advisory, vdb-entry
-
packetstormsecurity.com
/files/154904/CA-Performance-Management-Arbitrary-Command-Execution.html
third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2019/Oct/37
mailing-list, third-party-advisory
Sources
- CVE List CVE-2019-13657
- NVD CVE-2019-13657
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.