WID-SEC-W-2025-2562
Vulnerability from csaf_certbund - Published: 2025-11-11 23:00 - Updated: 2025-11-11 23:00Summary
Microsoft SQL Server: Schwachstelle ermöglicht Privilegieneskalation
Notes
Das BSI ist als Anbieter für die eigenen, zur Nutzung bereitgestellten Inhalte nach den allgemeinen Gesetzen verantwortlich. Nutzerinnen und Nutzer sind jedoch dafür verantwortlich, die Verwendung und/oder die Umsetzung der mit den Inhalten bereitgestellten Informationen sorgfältig im Einzelfall zu prüfen.
Produktbeschreibung
Der Microsoft SQL Server ist ein relationales Datenbankmanagementsystem von Microsoft.
Der Microsoft SQL Server ist ein relationales Datenbankmanagementsystem von Microsoft.
Angriff
Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Microsoft SQL Server 2017, Microsoft SQL Server 2019, Microsoft SQL Server 2016 und Microsoft SQL Server 2022 ausnutzen, um eine SQL-Injection durchzuführen und erhöhte Privilegien zu erlangen.
Betroffene Betriebssysteme
- Windows
{
"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": "Der Microsoft SQL Server ist ein relationales Datenbankmanagementsystem von Microsoft.\r\nDer Microsoft SQL Server ist ein relationales Datenbankmanagementsystem von Microsoft.",
"title": "Produktbeschreibung"
},
{
"category": "summary",
"text": "Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Microsoft SQL Server 2017, Microsoft SQL Server 2019, Microsoft SQL Server 2016 und Microsoft SQL Server 2022 ausnutzen, um eine SQL-Injection durchzuf\u00fchren und erh\u00f6hte Privilegien zu erlangen.",
"title": "Angriff"
},
{
"category": "general",
"text": "- Windows",
"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-2025-2562 - CSAF Version",
"url": "https://wid.cert-bund.de/.well-known/csaf/white/2025/wid-sec-w-2025-2562.json"
},
{
"category": "self",
"summary": "WID-SEC-2025-2562 - Portal Version",
"url": "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2025-2562"
},
{
"category": "external",
"summary": "Microsoft Leitfaden f\u00fcr Sicherheitsupdates",
"url": "https://msrc.microsoft.com/update-guide/"
}
],
"source_lang": "en-US",
"title": "Microsoft SQL Server: Schwachstelle erm\u00f6glicht Privilegieneskalation",
"tracking": {
"current_release_date": "2025-11-11T23:00:00.000+00:00",
"generator": {
"date": "2025-11-12T08:32:17.842+00:00",
"engine": {
"name": "BSI-WID",
"version": "1.4.0"
}
},
"id": "WID-SEC-W-2025-2562",
"initial_release_date": "2025-11-11T23:00:00.000+00:00",
"revision_history": [
{
"date": "2025-11-11T23:00:00.000+00:00",
"number": "1",
"summary": "Initiale Fassung"
}
],
"status": "final",
"version": "1"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version",
"name": "SP3 (GDR)",
"product": {
"name": "Microsoft SQL Server 2016 SP3 (GDR)",
"product_id": "T048472",
"product_identification_helper": {
"cpe": "cpe:/a:microsoft:sql_server_2016:sp3_%28gdr%29"
}
}
},
{
"category": "product_version",
"name": "SP3 Azure Connect Feature Pack",
"product": {
"name": "Microsoft SQL Server 2016 SP3 Azure Connect Feature Pack",
"product_id": "T048473",
"product_identification_helper": {
"cpe": "cpe:/a:microsoft:sql_server_2016:sp3_azure_connect_feature_pack"
}
}
}
],
"category": "product_name",
"name": "SQL Server 2016"
},
{
"branches": [
{
"category": "product_version",
"name": "(GDR)",
"product": {
"name": "Microsoft SQL Server 2017 (GDR)",
"product_id": "T048470",
"product_identification_helper": {
"cpe": "cpe:/a:microsoft:sql_server_2017:%28gdr%29"
}
}
},
{
"category": "product_version",
"name": "(CU 31)",
"product": {
"name": "Microsoft SQL Server 2017 (CU 31)",
"product_id": "T048474",
"product_identification_helper": {
"cpe": "cpe:/a:microsoft:sql_server_2017:%28cu_31%29"
}
}
}
],
"category": "product_name",
"name": "SQL Server 2017"
},
{
"branches": [
{
"category": "product_version",
"name": "(GDR)",
"product": {
"name": "Microsoft SQL Server 2019 (GDR)",
"product_id": "T048471",
"product_identification_helper": {
"cpe": "cpe:/a:microsoft:sql_server_2019:%28gdr%29"
}
}
},
{
"category": "product_version",
"name": "(CU 32)",
"product": {
"name": "Microsoft SQL Server 2019 (CU 32)",
"product_id": "T048476",
"product_identification_helper": {
"cpe": "cpe:/a:microsoft:sql_server_2019:%28cu_32%29"
}
}
}
],
"category": "product_name",
"name": "SQL Server 2019"
},
{
"branches": [
{
"category": "product_version",
"name": "(GDR)",
"product": {
"name": "Microsoft SQL Server 2022 (GDR)",
"product_id": "T048475",
"product_identification_helper": {
"cpe": "cpe:/a:microsoft:sql_server_2022:%28gdr%29"
}
}
},
{
"category": "product_version",
"name": "(CU 21)",
"product": {
"name": "Microsoft SQL Server 2022 (CU 21)",
"product_id": "T048477",
"product_identification_helper": {
"cpe": "cpe:/a:microsoft:sql_server_2022:%28cu_21%29"
}
}
}
],
"category": "product_name",
"name": "SQL Server 2022"
}
],
"category": "vendor",
"name": "Microsoft"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2025-59499",
"product_status": {
"known_affected": [
"T048472",
"T048471",
"T048470",
"T048476",
"T048475",
"T048474",
"T048473",
"T048477"
]
},
"release_date": "2025-11-11T23:00:00.000+00:00",
"title": "CVE-2025-59499"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
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.
Loading…
Loading…