Content spoofing via improper signature verification
Published Jan 26, 2024 · Updated May 3, 2025
Spoofing in Microsoft Edge before 121.0.2277.83 allows local users to alter presented identity information after user interaction. Microsoft classifies the issue as improper verification of a cryptographic signature but has not disclosed the affected Edge component, signed input, or incorrect verification operation. Exploitation requires a local user-interaction path and has a limited integrity impact, with no published confidentiality or availability impact.
Summary
What happened
Spoofing in Microsoft Edge before 121.0.2277.83 allows local users to alter presented identity information after user interaction. Microsoft classifies the issue as improper verification of a cryptographic signature but has not disclosed the affected Edge component, signed input, or incorrect verification operation. Exploitation requires a local user-interaction path and has a limited integrity impact, with no published confidentiality or availability impact.
The record
- CVE
- CVE-2024-21383
- Published
- Jan 26, 2024
- Updated
- May 3, 2025
- Vendor
- Microsoft
- Product
- Microsoft Edge (Chromium-based)
- Classifications
- CWE-347, CAPEC-475
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 26, 2024CVE publishedPublication date reported by the CVE source.
- May 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <121.0.2277.83
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo