Published on May 15th, 2019 📆 | 4533 Views ⚑
0Microsoft Edge memory corruption [CVE-2019-0926]
CVSS Meta Temp Score | Current Exploit Price (≈) |
---|---|
5.0 | $5k-$25k |
A vulnerability, which was classified as critical, was found in Microsoft Edge (Web Browser) (the affected version unknown). This affects a function. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was shared 05/14/2019 as confirmed security update guide (Website). It is possible to read the advisory at portal.msrc.microsoft.com. The vendor cooperated in the coordination of the public release. This vulnerability is uniquely identified as CVE-2019-0926. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 05/14/2019). The advisory points out:
A remote code execution vulnerability exists when Microsoft Edge improperly accesses objects in memory. The vulnerability could corrupt memory in such a way that enables an attacker to execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The issues 134683 are related to this entry.
Vendor
Name
VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: ?
VulDB Reliability: ?
Vendor Base Score (Microsoft): 4.2
Vendor Vector (Microsoft): ?
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
? | ? | ? | ? | ? | ? |
? | ? | ? | ? | ? | ? |
? | ? | ? | ? | ? | ? |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: ?
VulDB Temp Score: ?
VulDB Reliability: ?
Class: Memory corruption (CWE-119)
Local: No
Remote: Yes
Availability: ?
Status: Not defined
Price Prediction: ?
Current Price Estimation: ?
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Threat: ?
Adversaries: ?
Geopolitics: ?
Economy: ?
Predictions: ?
Remediation: ?Recommended: Patch
Status: ?
Reaction Time: ?
0-Day Time: ?
Exposure Time: ?05/14/2019 Advisory disclosed
05/14/2019 Countermeasure disclosed
05/14/2019 VulDB entry created
05/14/2019 VulDB last updateAdvisory: portal.msrc.microsoft.com
Status: Confirmed
Coordinated: ?
CVE: CVE-2019-0926 (?)
See also: ?
Created: 05/14/2019 09:07 PM
Complete: ?
Comments
Upgrade your account now!
https://vuldb.com/?id.134679
No comments yet. Please log in to comment.