{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-42791 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-42791 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-42791 is a high-severity missing authorization vulnerability in n/a, published on 28 Jan 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-42791 and fix it if it is affected.\n\nWhat it is: CVE-2021-42791 is a high-severity missing authorization vulnerability in n/a, published on 28 Jan 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-42791 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-42791/ (Markdown: https://insights.sbomify.com/CVE-2021-42791/index.md)","id":"CVE-2021-42791","markdown":"https://insights.sbomify.com/CVE-2021-42791/index.md","name":"CVE-2021-42791","record":{"aliases":["GHSA-4x8v-5q76-ppwc"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"VeridiumAD authentication server","requires_auth":"low_privilege","summary":"Attackers can trigger push notifications for other users and steal login certificates if notifications are accepted, leading to account takeover.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"veridiumad","vendor":"veridiumid"}],"cvss":{"score":7.3,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in n/a","id":"CVE-2021-42791","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2021-42792"},"packages":[],"prev":{"headline":"Directory Traversal Write/Delete/Partial Read at AgentConfigurationServlet","id":"CVE-2021-42787"},"products":["n/a"],"published":"2022-01-28","related":[{"cvss_score":9.1,"headline":"Auth bypass in n/a","id":"CVE-2023-44039","kev_date_added":null,"published":"2024-04-03"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2023-44038","kev_date_added":null,"published":"2024-04-03"},{"cvss_score":6.5,"headline":"Cross-site scripting in n/a","id":"CVE-2023-45552","kev_date_added":null,"published":"2024-04-03"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2023-44040","kev_date_added":null,"published":"2024-04-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can trigger push notifications for other users and steal login certificates if notifications are accepted, leading to account takeover.","url":"https://insights.sbomify.com/CVE-2021-42791/"}