dbcve.org
Rtl819x Jungle Software Development KitApplication · Realtek

CVE-2023-50383

HIGH · 7.2 CVSS v3.1 Published 2024-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Three os command injection vulnerabilities exist in the boa formWsc functionality of Realtek rtl819x Jungle SDK v3.4.11. A specially crafted series of HTTP requests can lead to arbitrary command execution. An attacker can send a series of HTTP requests to trigger these vulnerabilities.This command injection is related to the `localPin` request's parameter.

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 boa web server's formWsc functionality of Realtek rtl819x Jungle SDK v3.4.11. The localPin HTTP request parameter is not properly sanitized before being passed to a system shell, allowing arbitrary command execution.

MitigationImplement strict input validation and sanitization on the localPin parameter to remove shell metacharacters; upgrade to a patched SDK version if available; otherwise disable the affected wsc form functionality.

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
Rtl819x Jungle Software Development KitApplication
Affected:= 3.4.11
Wbr 6013 FirmwareOperating system
Affected:= rer4_a_v3411b_2t2r_lev_09_170623

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

CVSS:3.1/AV:N/AC:L/PR:H/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 the SDK or firmware version
    Check your device's firmware version or SDK documentation. For Level1 WBR-6013, look for version rer4_a_v3411b_2t2r_lev_09_170623. For Realtek rtl819x-based devices, determine if they run the Realtek Rtl819x Jungle Software Development Kit version 3.4.11.
    Affected if The installed firmware is version rer4_a_v3411b_2t2r_lev_09_170623 or the SDK version is exactly 3.4.11
  2. Verify the boa web server is present
    Check if the boa web server binary or service is running on the device. This is typically found in embedded router/firmware environments using the Realtek SDK.
    Affected if The boa web server is installed and running on the device
  3. Confirm formWsc functionality is exposed
    Determine if the WSC (Wi-Fi Simple Config) web form endpoint is accessible on the device. This is typically accessed via a web interface path related to WSC or wireless configuration.
    Affected if The formWsc web form functionality is enabled and reachable via HTTP
  4. Check for localPin parameter handling
    Inspect the boa web server configuration or the formWsc handler code for how the localPin HTTP parameter is processed. Look for direct use of this parameter in system calls.
    Affected if The localPin parameter from HTTP requests is passed to shell commands without sanitization
  5. Review logs for injection attempts
    Check system or web server logs for any suspicious localPin parameter values that may indicate command injection attempts.
    Affected if Logs show unusual localPin values containing shell metacharacters like ; | & $ or backticks

You are affected if your device runs the Realtek Rtl819x Jungle SDK version 3.4.11 or Level1 WBR-6013 firmware rer4_a_v3411b_2t2r_lev_09_170623, and the boa web server with formWsc functionality is enabled and accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization on the localPin parameter to remove shell metacharacters; upgrade to a patched SDK version if available; otherwise disable the affected wsc form functionality.

Fix this in Rtl819x Jungle Software Development Kit Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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