WID-SEC-W-2023-1160
Vulnerability from csaf_certbund - Published: 2023-05-07 22:00 - Updated: 2023-05-07 22:00Es existiert eine Schwachstelle in GitLab. Unter bestimmten Bedingungen kann jedes GitLab-Benutzerkonto auf der Instanz einen GraphQL-Endpunkt verwenden, um einen bösartigen Runner an ein beliebiges Projekt auf der Instanz anzuhängen. Ein authentisierter Angreifer kann diese Schwachstelle ausnutzen, um Sicherheitsvorkehrungen zu umgehen.
{
"document": {
"aggregate_severity": {
"text": "hoch"
},
"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": "GitLab ist eine Webanwendung zur Versionsverwaltung f\u00fcr Softwareprojekte auf Basis von git.",
"title": "Produktbeschreibung"
},
{
"category": "summary",
"text": "Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in GitLab ausnutzen, um Sicherheitsvorkehrungen zu umgehen.",
"title": "Angriff"
},
{
"category": "general",
"text": "- UNIX\n- Linux\n- Windows\n- 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-2023-1160 - CSAF Version",
"url": "https://wid.cert-bund.de/.well-known/csaf/white/2023/wid-sec-w-2023-1160.json"
},
{
"category": "self",
"summary": "WID-SEC-2023-1160 - Portal Version",
"url": "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2023-1160"
},
{
"category": "external",
"summary": "gitlGitLab Critical Security Release: 15.11.2, 15.10.6, and 15.9.7 vom 2023-05-07",
"url": "https://about.gitlab.com/releases/2023/05/05/critical-security-release-gitlab-15-11-2-released/"
}
],
"source_lang": "en-US",
"title": "GitLab: Schwachstelle erm\u00f6glicht Umgehen von Sicherheitsvorkehrungen",
"tracking": {
"current_release_date": "2023-05-07T22:00:00.000+00:00",
"generator": {
"date": "2024-08-15T17:50:30.193+00:00",
"engine": {
"name": "BSI-WID",
"version": "1.3.5"
}
},
"id": "WID-SEC-W-2023-1160",
"initial_release_date": "2023-05-07T22:00:00.000+00:00",
"revision_history": [
{
"date": "2023-05-07T22:00:00.000+00:00",
"number": "1",
"summary": "Initiale Fassung"
}
],
"status": "final",
"version": "1"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_name",
"name": "Open Source GitLab \u003c 15.11.2",
"product": {
"name": "Open Source GitLab \u003c 15.11.2",
"product_id": "T027638",
"product_identification_helper": {
"cpe": "cpe:/a:gitlab:gitlab:15.11.2"
}
}
},
{
"category": "product_name",
"name": "Open Source GitLab \u003c 15.10.6",
"product": {
"name": "Open Source GitLab \u003c 15.10.6",
"product_id": "T027639",
"product_identification_helper": {
"cpe": "cpe:/a:gitlab:gitlab:15.10.6"
}
}
},
{
"category": "product_name",
"name": "Open Source GitLab \u003c 15.9.7",
"product": {
"name": "Open Source GitLab \u003c 15.9.7",
"product_id": "T027640",
"product_identification_helper": {
"cpe": "cpe:/a:gitlab:gitlab:15.9.7"
}
}
}
],
"category": "product_name",
"name": "GitLab"
}
],
"category": "vendor",
"name": "Open Source"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2023-2478",
"notes": [
{
"category": "description",
"text": "Es existiert eine Schwachstelle in GitLab. Unter bestimmten Bedingungen kann jedes GitLab-Benutzerkonto auf der Instanz einen GraphQL-Endpunkt verwenden, um einen b\u00f6sartigen Runner an ein beliebiges Projekt auf der Instanz anzuh\u00e4ngen. Ein authentisierter Angreifer kann diese Schwachstelle ausnutzen, um Sicherheitsvorkehrungen zu umgehen."
}
],
"release_date": "2023-05-07T22:00:00.000+00:00",
"title": "CVE-2023-2478"
}
]
}
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.