# CVE-2019-13658: Hardcoded credentials in CA Network Flow Analysis

> Remote attackers can exploit default credentials in CA Network Flow Analysis to execute arbitrary commands and compromise the system.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4rg6-4q55-x5wx

## What is CVE-2019-13658?

CVE-2019-13658 is a critical vulnerability in CA Network Flow Analysis, published on 2 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CA Network Flow Analysis 9.x and 10.0.x have a default credential vulnerability that can allow a remote attacker to execute arbitrary commands and compromise system security.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2019-13658?

It affects 1 product.


Products: Broadcom Network Flow Analysis.

## How do I fix CVE-2019-13658?

No fix has been published for CVE-2019-13658 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-13658 being exploited?

There is no known exploitation of CVE-2019-13658 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13658 and fix it if it is affected.

What it is: CVE-2019-13658 is a critical vulnerability in CA Network Flow Analysis, published on 2 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-13658 in the wild and no public exploit code.

Affected product: CA Network Flow Analysis. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-13658/ (Markdown: https://insights.sbomify.com/CVE-2019-13658/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-13658
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-13658
- OSV: https://osv.dev/vulnerability/CVE-2019-13658

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-13658/
Summaries are generated and may contain mistakes; the official description above is the record.