WID-SEC-W-2023-1966
Vulnerability from csaf_certbund - Published: 2020-11-10 23:00 - Updated: 2023-08-03 22:00Es existiert eine Schwachstelle in X.Org X11. X11 Clients (Anwendungen) überprüfen die Identität des X11 Servers (Display-Server) nicht, sondern nutzen in der Regel ohne weitere Prüfung den X11 Socket in "/tmp/.X11-unix". Ein lokaler Angreifer kann, wenn dieser Socket nicht belegt ist, diesen übernehmen. Verbindet sich dann eine Anwendung mit dem Socket, hat der Angreifer die Kontrolle darüber.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
SUSE Linux
SUSE
|
cpe:/o:suse:suse_linux:-
|
— | |
|
Open Source X.Org X11
Open Source
|
cpe:/a:x:x.org_x11:-
|
— |
{
"document": {
"aggregate_severity": {
"text": "niedrig"
},
"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": "Das X Window System dient der Erzeugung grafischer Oberfl\u00e4chen auf Unix Systemen.",
"title": "Produktbeschreibung"
},
{
"category": "summary",
"text": "Ein lokaler Angreifer kann eine Schwachstelle in X.Org X11 ausnutzen, um seine Privilegien zu erh\u00f6hen.",
"title": "Angriff"
},
{
"category": "general",
"text": "- UNIX\n- Linux",
"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-2023-1966 - CSAF Version",
"url": "https://wid.cert-bund.de/.well-known/csaf/white/2020/wid-sec-w-2023-1966.json"
},
{
"category": "self",
"summary": "WID-SEC-2023-1966 - Portal Version",
"url": "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2023-1966"
},
{
"category": "external",
"summary": "SUSE Security Update SUSE-SU-2023:3189-1 vom 2023-08-04",
"url": "https://lists.suse.com/pipermail/sle-security-updates/2023-August/015782.html"
},
{
"category": "external",
"summary": "SUSE Security Update SUSE-SU-2023:3190-1 vom 2023-08-04",
"url": "https://lists.suse.com/pipermail/sle-security-updates/2023-August/015781.html"
},
{
"category": "external",
"summary": "Mailing list OSS-Security vom 2020-11-09",
"url": "http://seclists.org/oss-sec/2020/q4/105"
}
],
"source_lang": "en-US",
"title": "X.Org X11: Schwachstelle erm\u00f6glicht Privilegieneskalation",
"tracking": {
"current_release_date": "2023-08-03T22:00:00.000+00:00",
"generator": {
"date": "2024-08-15T17:56:34.724+00:00",
"engine": {
"name": "BSI-WID",
"version": "1.3.5"
}
},
"id": "WID-SEC-W-2023-1966",
"initial_release_date": "2020-11-10T23:00:00.000+00:00",
"revision_history": [
{
"date": "2020-11-10T23:00:00.000+00:00",
"number": "1",
"summary": "Initiale Fassung"
},
{
"date": "2023-08-03T22:00:00.000+00:00",
"number": "2",
"summary": "Neue Updates von SUSE aufgenommen"
}
],
"status": "final",
"version": "2"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"category": "product_name",
"name": "Open Source X.Org X11",
"product": {
"name": "Open Source X.Org X11",
"product_id": "T001034",
"product_identification_helper": {
"cpe": "cpe:/a:x:x.org_x11:-"
}
}
}
],
"category": "vendor",
"name": "Open Source"
},
{
"branches": [
{
"category": "product_name",
"name": "SUSE Linux",
"product": {
"name": "SUSE Linux",
"product_id": "T002207",
"product_identification_helper": {
"cpe": "cpe:/o:suse:suse_linux:-"
}
}
}
],
"category": "vendor",
"name": "SUSE"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2020-25697",
"notes": [
{
"category": "description",
"text": "Es existiert eine Schwachstelle in X.Org X11. X11 Clients (Anwendungen) \u00fcberpr\u00fcfen die Identit\u00e4t des X11 Servers (Display-Server) nicht, sondern nutzen in der Regel ohne weitere Pr\u00fcfung den X11 Socket in \"/tmp/.X11-unix\". Ein lokaler Angreifer kann, wenn dieser Socket nicht belegt ist, diesen \u00fcbernehmen. Verbindet sich dann eine Anwendung mit dem Socket, hat der Angreifer die Kontrolle dar\u00fcber."
}
],
"product_status": {
"known_affected": [
"T002207",
"T001034"
]
},
"release_date": "2020-11-10T23:00:00.000+00:00",
"title": "CVE-2020-25697"
}
]
}
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.