BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2023
CVE-2023-2861High confidence

Qemu: 9pfs: improper access control on special files

Unknown · Unknown

Official source article: Siemens SSA-806742 ↗. Check the applicable product and release in the original source.

6.0MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 11 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.38% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 11 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · communityqemuVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.8.0.2-r1Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · communityqemuVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.8.0.2-r1Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.21v3.21 · communityqemuVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.8.0.2-r1Alpine Security Database ↗Source updated 19 Aug 2026
Debian trixietrixie · sourceqemuVendor fix publishedDebian records a fixed source-package version for this release.1:8.0.3+dfsg-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourceqemuVendor fix publishedDebian records a fixed source-package version for this release.1:7.2+dfsg-7+deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourceqemuVendor fix publishedDebian records a fixed source-package version for this release.1:8.0.3+dfsg-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourceqemuVendor fix publishedDebian records a fixed source-package version for this release.1:8.0.3+dfsg-1Debian Security Tracker ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
SSA-806742 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-806742: Multiple Vulnerabilities in SCALANCE XCM-/XRM-300 before V2.4
11 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SCALANCE XCH328 (6GK5328-4TS01-2EC2)
  • SCALANCE XCM324 (6GK5324-8TS01-2AC2)
  • SCALANCE XCM328 (6GK5328-4TS01-2AC2)
  • SCALANCE XCM332 (6GK5332-0GA01-2AC2)
  • SCALANCE XRH334 (24 V DC, 8xFO, CC) (6GK5334-2TS01-2ER3)
  • SCALANCE XRM334 (230 V AC, 12xFO) (6GK5334-3TS01-3AR3)
  • SCALANCE XRM334 (230 V AC, 8xFO) (6GK5334-2TS01-3AR3)
  • SCALANCE XRM334 (24 V DC, 12xFO) (6GK5334-3TS01-2AR3)
  • SCALANCE XRM334 (24 V DC, 8xFO) (6GK5334-2TS01-2AR3)
  • SCALANCE XRM334 (2x230 V AC, 12xFO) (6GK5334-3TS01-4AR3)
  • SCALANCE XRM334 (2x230 V AC, 8xFO) (6GK5334-2TS01-4AR3)
Summary
A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. The 9pfs server did not prohibit opening special files on the host side, potentially allowing a malicious client to escape from the exported 9p tree by creating and opening a device file in the shared folder.
Remediation
Update to V2.4 or later version
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2023-34310

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 11 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. The 9pfs server did not prohibit opening special files on the host side, potentially allowing a malicious client to escape from the exported 9p tree by creating and opening a device file in the shared folder.

What

A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. The 9pfs server did not prohibit opening special files on the host side, potentially allowing a malicious client to escape from the exported 9p tree by creating and opening a device file in the shared folder.

Why

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How

An attacker operating through local access may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. The 9pfs server did not prohibit opening special files on the host side, potentially allowing a malicious client to escape from the exported 9p tree by creating and opening a device file in the shared folder.

Why

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How

An attacker operating through local access may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.

Likely attack path
local access → Improper Access Control → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
High: elevated access is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-284 ↗

CWE-284: Improper Access Control. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-284Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2023-1755IBM InfoSphere Information Server: Mehrere Schwachstellen

Ein entfernter, anonymer, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in IBM InfoSphere Information Server ausnutzen, um beliebigen Programmcode auszuführen, Sicherheitsvorkehrungen zu umgehen oder einen Denial of Service Zustand herbeizuführen.

Official advisory ↗
BSI · German · WID-SEC-2023-1621QEMU: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

Ein lokaler Angreifer kann eine Schwachstelle in QEMU ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20231213Security Bulletin 13 Dec 2023

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 13 Dec 2023, published on 13 December 2023. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0619Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2022-47007 Référence CVE CVE-2022-47008 https://www.cve.org/CVERecord?id=CVE-2022-47008 Référence CVE CVE-2022-47010 https://www.cve.org/CVERecord?id=CVE-2022-47010 Référence CVE CVE-2022-47011 https://www.cve.org/CVERecord?id=CVE-2022-47011 Référence CVE CVE-2022-47015 https://www.cve.org/CVERecord?id=CVE-2022-47015 Référence CVE CVE-2023-1544 https://www.cve.org/CVERecord?id=CVE-2023-1544 Référence CVE CVE-2023-22028 https://www.cve.org/CVERecord?id=CVE-2023-22028 Référence CVE CVE-2023-22084 https://www.cve.org/CVERecord?id=CVE-2023-22084 Référence CVE CVE-2023-23931 https://www.cve.org/CVERecord?id=CVE-2023-23931 Référence CVE CVE-2023-2861 https://www.cve.org/CVERecord?id=CVE-2023-2861 Référence CVE CVE-2023-3180 https://www.cve.org/CVERecord?id=CVE-2023-3180 Référence CVE CVE-2023-3255 https://www.cve.org/CVERecord?id=CVE-2023-3255 Référence CVE CVE-2023-3301 https://www.cve.org/CVERecord?id=CVE-2023-3301 Référence CVE CVE-2023-3354 https://www.cve.org/CVERecord?id=CVE-2023-3354 Référence CVE CVE-2023-40360 https://www.cve.org/CVERecord?id=CVE-2023-40360 Référence CVE CVE-2023-4135 https://www.cve.org/CVERecord?id=CVE-2023-4135 Référence CVE CVE-2023-42467 https://www.cve.org/CVERecord?id=CVE-2023-42467 Référence CVE CVE-2023-49083 https://www.cve.org/CVERecord?id=CVE-2023-49

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0119Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2023-27538 Référence CVE CVE-2023-28319 https://www.cve.org/CVERecord?id=CVE-2023-28319 Référence CVE CVE-2023-28320 https://www.cve.org/CVERecord?id=CVE-2023-28320 Référence CVE CVE-2023-28321 https://www.cve.org/CVERecord?id=CVE-2023-28321 Référence CVE CVE-2023-28322 https://www.cve.org/CVERecord?id=CVE-2023-28322 Référence CVE CVE-2023-28450 https://www.cve.org/CVERecord?id=CVE-2023-28450 Référence CVE CVE-2023-28466 https://www.cve.org/CVERecord?id=CVE-2023-28466 Référence CVE CVE-2023-28486 https://www.cve.org/CVERecord?id=CVE-2023-28486 Référence CVE CVE-2023-28487 https://www.cve.org/CVERecord?id=CVE-2023-28487 Référence CVE CVE-2023-2861 https://www.cve.org/CVERecord?id=CVE-2023-2861 Référence CVE CVE-2023-28709 https://www.cve.org/CVERecord?id=CVE-2023-28709 Référence CVE CVE-2023-29402 https://www.cve.org/CVERecord?id=CVE-2023-29402 Référence CVE CVE-2023-29404 https://www.cve.org/CVERecord?id=CVE-2023-29404 Référence CVE CVE-2023-29405 https://www.cve.org/CVERecord?id=CVE-2023-29405 Référence CVE CVE-2023-29406 https://www.cve.org/CVERecord?id=CVE-2023-29406 Référence CVE CVE-2023-29409 https://www.cve.org/CVERecord?id=CVE-2023-29409 Référence CVE CVE-2023-2953 https://www.cve.org/CVERecord?id=CVE-2023-2953 Référence CVE CVE-2023-2975 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-018933Fabrice Bellard の QEMU における脆弱性

Fabrice Bellard の QEMU には、不特定の脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
8.1.0-rc0 < *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 6 Dec 2023 · Last source change 2 Aug 2024, 06:33 UTC · CWE-284 · Improper Access Control

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2023-34310
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceCNA
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-2861 · cve.blacktree.nl