WID-SEC-W-2024-1348
Vulnerability from csaf_certbund - Published: 2024-06-11 22:00 - Updated: 2024-06-11 22:00In Samsung Exynos bestehen mehrere Schwachstellen. Diese Fehler sind auf unsachgemäße Längen- und Pufferprüfungen zurückzuführen, was zu einem Out-of-Bound-Write-Problem führt. Ein entfernter, anonymer Angreifer kann diese Schwachstelle zur Ausführung von beliebigem Code ausnutzen. Für eine erfolgreiche Ausnutzung ist entweder eine Anmeldung oder eine Interaktion des Nutzers nötig.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Samsung Exynos Exynos 2200
Samsung / Exynos
|
cpe:/h:samsung:exynos:exynos_2200
|
Exynos 2200 | |
|
Samsung Exynos Exynos 2100
Samsung / Exynos
|
cpe:/h:samsung:exynos:exynos_2100
|
Exynos 2100 | |
|
Samsung Exynos Exynos 1480
Samsung / Exynos
|
cpe:/h:samsung:exynos:exynos_1480
|
Exynos 1480 | |
|
Samsung Exynos Exynos W930
Samsung / Exynos
|
cpe:/h:samsung:exynos:exynos_w930
|
Exynos W930 | |
|
Samsung Exynos Exynos W920
Samsung / Exynos
|
cpe:/h:samsung:exynos:exynos_w920
|
Exynos W920 | |
|
Samsung Exynos Exynos 1280
Samsung / Exynos
|
cpe:/h:samsung:exynos:exynos_1280
|
Exynos 1280 | |
|
Samsung Exynos Exynos 1080
Samsung / Exynos
|
cpe:/h:samsung:exynos:exynos_1080
|
Exynos 1080 | |
|
Samsung Exynos Exynos 850
Samsung / Exynos
|
cpe:/h:samsung:exynos:exynos_850
|
Exynos 850 | |
|
Samsung Exynos Exynos 2400
Samsung / Exynos
|
cpe:/h:samsung:exynos:exynos_2400
|
Exynos 2400 | |
|
Samsung Exynos Exynos 1330
Samsung / Exynos
|
cpe:/h:samsung:exynos:exynos_1330
|
Exynos 1330 | |
|
Samsung Exynos Exynos 1380
Samsung / Exynos
|
cpe:/h:samsung:exynos:exynos_1380
|
Exynos 1380 |
In Samsung Exynos bestehen mehrere Schwachstellen. Diese Fehler sind auf unsachgemäße Längen- und Pufferprüfungen zurückzuführen, was zu einem Out-of-Bound-Write-Problem führt. Ein entfernter, anonymer Angreifer kann diese Schwachstelle zur Ausführung von beliebigem Code ausnutzen. Für eine erfolgreiche Ausnutzung ist entweder eine Anmeldung oder eine Interaktion des Nutzers nötig.
{
"document": {
"aggregate_severity": {
"text": "mittel"
},
"category": "csaf_base",
"csaf_version": "2.0",
"distribution": {
"tlp": {
"label": "WHITE",
"url": "https://www.first.org/tlp/"
}
},
"lang": "de-DE",
"notes": [
{
"category": "legal_disclaimer",
"text": "Das BSI ist als Anbieter f\u00fcr die eigenen, zur Nutzung bereitgestellten Inhalte nach den allgemeinen Gesetzen verantwortlich. Nutzerinnen und Nutzer sind jedoch daf\u00fcr verantwortlich, die Verwendung und/oder die Umsetzung der mit den Inhalten bereitgestellten Informationen sorgf\u00e4ltig im Einzelfall zu pr\u00fcfen."
},
{
"category": "description",
"text": "Exynos ist der Markenname f\u00fcr Samsung-Mobilfunk-Chips\u00e4tze und Prozessoren.",
"title": "Produktbeschreibung"
},
{
"category": "summary",
"text": "Ein Angreifer kann mehrere Schwachstellen in Samsung Exynos ausnutzen, um beliebigen Programmcode auszuf\u00fchren.",
"title": "Angriff"
},
{
"category": "general",
"text": "- Sonstiges",
"title": "Betroffene Betriebssysteme"
}
],
"publisher": {
"category": "other",
"contact_details": "csaf-provider@cert-bund.de",
"name": "Bundesamt f\u00fcr Sicherheit in der Informationstechnik",
"namespace": "https://www.bsi.bund.de"
},
"references": [
{
"category": "self",
"summary": "WID-SEC-W-2024-1348 - CSAF Version",
"url": "https://wid.cert-bund.de/.well-known/csaf/white/2024/wid-sec-w-2024-1348.json"
},
{
"category": "self",
"summary": "WID-SEC-2024-1348 - Portal Version",
"url": "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2024-1348"
},
{
"category": "external",
"summary": "Samsung Product Security Update vom 2024-06-11",
"url": "https://semiconductor.samsung.com/content/semiconductor/global/support/quality-support/product-security-updates/cve-2024-31956/"
},
{
"category": "external",
"summary": "Samsung Product Security Update vom 2024-06-11",
"url": "https://semiconductor.samsung.com/content/semiconductor/global/support/quality-support/product-security-updates/cve-2024-32504/"
}
],
"source_lang": "en-US",
"title": "Samsung Exynos: Mehrere Schwachstellen erm\u00f6glichen Codeausf\u00fchrung",
"tracking": {
"current_release_date": "2024-06-11T22:00:00.000+00:00",
"generator": {
"date": "2024-08-15T18:10:04.962+00:00",
"engine": {
"name": "BSI-WID",
"version": "1.3.5"
}
},
"id": "WID-SEC-W-2024-1348",
"initial_release_date": "2024-06-11T22:00:00.000+00:00",
"revision_history": [
{
"date": "2024-06-11T22:00:00.000+00:00",
"number": "1",
"summary": "Initiale Fassung"
}
],
"status": "final",
"version": "1"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version",
"name": "Exynos 2200",
"product": {
"name": "Samsung Exynos Exynos 2200",
"product_id": "T035359",
"product_identification_helper": {
"cpe": "cpe:/h:samsung:exynos:exynos_2200"
}
}
},
{
"category": "product_version",
"name": "Exynos 1480",
"product": {
"name": "Samsung Exynos Exynos 1480",
"product_id": "T035360",
"product_identification_helper": {
"cpe": "cpe:/h:samsung:exynos:exynos_1480"
}
}
},
{
"category": "product_version",
"name": "Exynos 2400",
"product": {
"name": "Samsung Exynos Exynos 2400",
"product_id": "T035361",
"product_identification_helper": {
"cpe": "cpe:/h:samsung:exynos:exynos_2400"
}
}
},
{
"category": "product_version",
"name": "Exynos 850",
"product": {
"name": "Samsung Exynos Exynos 850",
"product_id": "T035362",
"product_identification_helper": {
"cpe": "cpe:/h:samsung:exynos:exynos_850"
}
}
},
{
"category": "product_version",
"name": "Exynos 1080",
"product": {
"name": "Samsung Exynos Exynos 1080",
"product_id": "T035363",
"product_identification_helper": {
"cpe": "cpe:/h:samsung:exynos:exynos_1080"
}
}
},
{
"category": "product_version",
"name": "Exynos 2100",
"product": {
"name": "Samsung Exynos Exynos 2100",
"product_id": "T035369",
"product_identification_helper": {
"cpe": "cpe:/h:samsung:exynos:exynos_2100"
}
}
},
{
"category": "product_version",
"name": "Exynos 1280",
"product": {
"name": "Samsung Exynos Exynos 1280",
"product_id": "T035375",
"product_identification_helper": {
"cpe": "cpe:/h:samsung:exynos:exynos_1280"
}
}
},
{
"category": "product_version",
"name": "Exynos 1380",
"product": {
"name": "Samsung Exynos Exynos 1380",
"product_id": "T035378",
"product_identification_helper": {
"cpe": "cpe:/h:samsung:exynos:exynos_1380"
}
}
},
{
"category": "product_version",
"name": "Exynos 1330",
"product": {
"name": "Samsung Exynos Exynos 1330",
"product_id": "T035379",
"product_identification_helper": {
"cpe": "cpe:/h:samsung:exynos:exynos_1330"
}
}
},
{
"category": "product_version",
"name": "Exynos W920",
"product": {
"name": "Samsung Exynos Exynos W920",
"product_id": "T035380",
"product_identification_helper": {
"cpe": "cpe:/h:samsung:exynos:exynos_w920"
}
}
},
{
"category": "product_version",
"name": "Exynos W930",
"product": {
"name": "Samsung Exynos Exynos W930",
"product_id": "T035381",
"product_identification_helper": {
"cpe": "cpe:/h:samsung:exynos:exynos_w930"
}
}
}
],
"category": "product_name",
"name": "Exynos"
}
],
"category": "vendor",
"name": "Samsung"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2024-31956",
"notes": [
{
"category": "description",
"text": "In Samsung Exynos bestehen mehrere Schwachstellen. Diese Fehler sind auf unsachgem\u00e4\u00dfe L\u00e4ngen- und Pufferpr\u00fcfungen zur\u00fcckzuf\u00fchren, was zu einem Out-of-Bound-Write-Problem f\u00fchrt. Ein entfernter, anonymer Angreifer kann diese Schwachstelle zur Ausf\u00fchrung von beliebigem Code ausnutzen. F\u00fcr eine erfolgreiche Ausnutzung ist entweder eine Anmeldung oder eine Interaktion des Nutzers n\u00f6tig."
}
],
"product_status": {
"known_affected": [
"T035359",
"T035369",
"T035360",
"T035381",
"T035380",
"T035375",
"T035363",
"T035362",
"T035361",
"T035379",
"T035378"
]
},
"release_date": "2024-06-11T22:00:00.000+00:00",
"title": "CVE-2024-31956"
},
{
"cve": "CVE-2024-32504",
"notes": [
{
"category": "description",
"text": "In Samsung Exynos bestehen mehrere Schwachstellen. Diese Fehler sind auf unsachgem\u00e4\u00dfe L\u00e4ngen- und Pufferpr\u00fcfungen zur\u00fcckzuf\u00fchren, was zu einem Out-of-Bound-Write-Problem f\u00fchrt. Ein entfernter, anonymer Angreifer kann diese Schwachstelle zur Ausf\u00fchrung von beliebigem Code ausnutzen. F\u00fcr eine erfolgreiche Ausnutzung ist entweder eine Anmeldung oder eine Interaktion des Nutzers n\u00f6tig."
}
],
"product_status": {
"known_affected": [
"T035359",
"T035369",
"T035360",
"T035381",
"T035380",
"T035375",
"T035363",
"T035362",
"T035361",
"T035379",
"T035378"
]
},
"release_date": "2024-06-11T22:00:00.000+00:00",
"title": "CVE-2024-32504"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.