Veridium VeridiumAD 2.5.3.0
Approved changes feed: RSS · Atom
cpe:2.3:a:veridiumid:veridiumad:2.5.3.0:*:*:*:*:*:*:*part: a version: 2.5.3.0 update: *
| Vendor | Veridiumid (48887128-916d-5281-9bae-1e664bdbf092) |
|---|---|
| Product | Veridiumad (68ae977b-9fd8-5400-91bf-7824ceaf6f10) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from NVD CPE 2.0 feed
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-42791 |
vulnerable | 2026-06-08 05:35:22.946346 |
Details available
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.
Published: 2022-01-28T13:01:22.000Z
Updated: 2024-08-04T03:38:50.166Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.