dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-48895

HIGH · 8.8 CVSS v3.1 Published 2024-11-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Improper neutralization of special elements used in an OS command ('OS Command Injection') issue exists in Rakuten Turbo 5G firmware version V1.3.18 and earlier. If this vulnerability is exploited, a remote authenticated attacker may execute an arbitrary OS command.

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 · high confidence

OS command injection vulnerability in the management interface of Rakuten Turbo 5G devices running firmware V1.3.18 and earlier allows remote authenticated attackers to execute arbitrary operating system commands due to improper neutralization of special elements in user input fields.

MitigationUpdate device firmware to a version newer than V1.3.18 when available; if no patch exists, disable remote administrative access and implement network segmentation to limit exposure to the device management interface.

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

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 device firmware version
    Access the device administrative interface or check the device settings panel for the firmware version information. On most routers/mobile hotspots, this is found under Settings > Device Info or About Device. Alternatively, check the web management console or the mobile app connected to the device.
    Affected if The firmware version is V1.3.18 or any version earlier than V1.3.19
  2. Confirm remote administrative access is enabled
    Check the device configuration for remote management or remote administration settings. This is typically found under Settings > Remote Management, Administration > Remote Access, or similar menu paths. Verify whether HTTP/HTTPS remote access to the admin interface is enabled.
    Affected if Remote administrative access is enabled and the device is reachable over the network
  3. Verify authentication is required for remote access
    Review the device security settings to confirm that remote administrative access requires valid credentials. Check if there are any misconfigurations that allow unauthenticated access to command injection points.
    Affected if Remote access is enabled and the device accepts authenticated sessions (attacker needs valid credentials per CVE description)
  4. Check for exposed input handling interfaces
    If you have access to the device logs or can test the administrative interface, look for input fields that accept user data and could be passed to system shell commands (e.g., network configuration fields, diagnostic tools, custom scripts).
    Affected if The device has input fields or API endpoints that accept user-supplied data without strict validation

The device is affected if it is running Rakuten Turbo 5G firmware V1.3.18 or earlier AND has remote administrative access enabled with authentication capabilities.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update device firmware to a version newer than V1.3.18 when available; if no patch exists, disable remote administrative access and implement network segmentation to limit exposure to the device management interface.

Recommended fix Moderate confidence

Firmware version newer than V1.3.18 (contact Rakuten for the exact fixed release number)

  1. 1. Identify the current firmware version of the Rakuten Turbo 5G device via the administrative web interface or device settings.
  2. 2. Navigate to the official Rakuten support or network.mobile.rakuten.co.jp website to check for available firmware updates.
  3. 3. Download the latest firmware version (newer than V1.3.18) from the official vendor source.
  4. 4. Follow the vendor's documented firmware upgrade procedure, typically accessible through the device's administrative interface.
  5. 5. After upgrading, verify the device is running the patched firmware version.
  6. 6. If remote management interfaces are not required, consider disabling them to reduce the attack surface as an additional hardening measure.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-48895 — 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-2024-48895 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