dbcve.org
Nexo OsOperating system · Bosch

CVE-2023-48248

MEDIUM · 5.4 CVSS v3.1 Published 2024-01-10
Fix available
A fix is available. Upgrade to after 1500-sp2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The vulnerability allows an authenticated remote attacker to upload a malicious file to the SD card containing arbitrary client-side script code and obtain its execution inside a victim’s session via a crafted URL, HTTP request, or simply by waiting for the victim to view the poisoned file.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a stored cross-site scripting (XSS) vulnerability in a system with SD card storage. An authenticated attacker can upload files containing malicious client-side script (e.g., HTML with embedded JavaScript) to the SD card. When other authenticated users view or access these poisoned files (via URL, HTTP request, or file browsing), the attacker's script executes within the victim's browser session, potentially stealing session cookies or performing actions as the victim.

MitigationImplement strict input validation and content-type restrictions on file uploads to the SD card, serve uploaded files with proper Content-Disposition headers and Content-Security-Policy, and sanitize or reject files containing executable client-side code (HTML, JavaScript, VBScript).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nexo OsOperating system
Affected:>= 1000, <= 1500-sp2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Bosch Nexo Os version
    Locate the system version information in the device management interface, firmware metadata, or system settings panel. Common locations include About section, firmware details, or diagnostic logs.
    Affected if The installed version falls within the range 1000 to 1500-sp2 (inclusive). Versions outside this range are not affected.
  2. Confirm SD card storage is enabled
    Check the system configuration or storage settings to verify whether the SD card storage feature is active. Look for SD card mount status, storage path configuration, or device status in the admin interface.
    Affected if SD card storage is mounted and accessible. Without an active SD card, the upload vector does not exist.
  3. Verify file upload capability to SD card
    Locate the file upload or file management functionality within the authenticated interface. Check if there is an option to upload, import, or transfer files to the SD card storage area.
    Affected if Authenticated users have the ability to upload files directly to the SD card storage. If upload to SD card is not available, the attack path is blocked.
  4. Check if uploaded files are accessible via web interface
    Determine whether files stored on the SD card can be accessed through HTTP requests, URL links, or file browsing features within the application.
    Affected if Uploaded files on the SD card are reachable through web URLs or file browsing. If files are not served or accessible, the XSS cannot be triggered.
  5. Inspect HTTP response headers for served files
    Access a file stored on the SD card through the web interface and examine the HTTP response headers, specifically looking for Content-Disposition and Content-Security-Policy headers.
    Affected if Files are served without Content-Disposition: attachment or without restrictive CSP headers, allowing HTML/JavaScript content to execute in the browser.

You are affected if your Bosch Nexo Os version is between 1000 and 1500-sp2, SD card storage is enabled, authenticated users can upload files to the SD card, and those files are accessible via the web interface without proper Content-Disposition or CSP protections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1500-sp2
Interim mitigation

Implement strict input validation and content-type restrictions on file uploads to the SD card, serve uploaded files with proper Content-Disposition headers and Content-Security-Policy, and sanitize or reject files containing executable client-side code (HTML, JavaScript, VBScript).

Fix this in Nexo Os Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-48248 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-48248 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data