CVE-2018-10751
published 2018-05-29CVE-2018-10751: A malformed OMACP WAP push message can cause memory corruption on a Samsung S7 Edge device when processing the String Extension portion of the WbXml payload…
PriorityP339medium5.3CVSS 3.0
AVNACHPRNUIRSUCNINAH
EXPLOIT
EPSS
8.75%
94.5th percentile
A malformed OMACP WAP push message can cause memory corruption on a Samsung S7 Edge device when processing the String Extension portion of the WbXml payload. This is due to an integer overflow in memory allocation for this string. The Samsung ID is SVE-2018-11463.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| samsung | samsung_mobile | — | — |
| samsung | samsung_mobile | — | — |
| samsung | samsung_mobile | — | — |
| samsung | samsung_mobile | — | — |
| samsung | samsung_mobile | — | — |
CVSS provenance
nvdv3.05.3MEDIUMCVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H
nvdv2.05.4MEDIUMAV:N/AC:H/Au:N/C:N/I:N/A:C
CVEs like this are exactly what “Exploited This Week” covers.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-p6q3-c5p7-24j9: A malformed OMACP WAP push message can cause memory corruption on a Samsung S7 Edge device when processing the String Extension portion of the WbXml p
ghsa_unreviewed·2022-05-14
CVE-2018-10751 [MEDIUM] CWE-190 GHSA-p6q3-c5p7-24j9: A malformed OMACP WAP push message can cause memory corruption on a Samsung S7 Edge device when processing the String Extension portion of the WbXml p
A malformed OMACP WAP push message can cause memory corruption on a Samsung S7 Edge device when processing the String Extension portion of the WbXml payload. This is due to an integer overflow in memory allocation for this string. The Samsung ID is SVE-2018-11463.
Project0
Adventures in vulnerability reporting - Project Zero
project_zero·2018-08-01
CVE-2016-7990 Adventures in vulnerability reporting - Project Zero
Posted by Natalie Silvanovich, Project Zero
At Project Zero, we spend a lot of time reporting security bugs to vendors. Most of the time, this is a fairly straightforward process, but we occasionally encounter challenges getting information about vulnerabilities into the hands of vendors. Since it is important to user security that software vendors fix reported vulnerabilities in a timely matter, and vendors need to actually receive the report for this to happen, we have decided to share some of our experiences. We hope to show that good practices by software vendors can avoid delays in vulnerability reporting.
Effective Vulnerability Reporting Processes
There are several aspects of a bug reporting process that make reporting vulnerabilities easier from the bug reporter’s perspective.
No detection rules found.
No writeups or analysis indexed.
http://packetstormsecurity.com/files/147841/Samsung-Galaxy-S7-Edge-OMACP-WbXml-String-Extension-Processing-Overflow.htmlhttps://security.samsungmobile.com/securityUpdate.smsbhttps://www.exploit-db.com/exploits/44724/http://packetstormsecurity.com/files/147841/Samsung-Galaxy-S7-Edge-OMACP-WbXml-String-Extension-Processing-Overflow.htmlhttps://security.samsungmobile.com/securityUpdate.smsbhttps://www.exploit-db.com/exploits/44724/
2018-05-29
Published