dbcve.org
Rtl819x Jungle Software Development KitApplication · Realtek

CVE-2023-49867

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
A stack-based buffer overflow vulnerability exists in the boa formWsc functionality of Realtek rtl819x Jungle SDK v3.4.11. A specially crafted series of HTTP requests can lead to remote code execution. An attacker can send a series of HTTP requests to trigger this vulnerability.

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

A stack-based buffer overflow vulnerability exists in the boa web server's formWsc functionality within the Realtek rtl819x Jungle SDK v3.4.11. The vulnerability is triggered by sending specially crafted HTTP requests that overflow a stack-allocated buffer, allowing an attacker to overwrite return addresses and achieve remote code execution.

MitigationApply any available vendor firmware updates for affected Realtek-based devices. If no update exists, consider disabling the WSC (Wi-Fi Simple Config) web interface functionality or implementing input length validation on the formWsc handler.

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 the system information or web interface for the Realtek rtl819x Jungle SDK version or Level1 WBR 6013 firmware version. This is typically found in the device's admin panel under 'Status' or 'System Information', or via command line if you have shell access (e.g., 'cat /proc/version', 'uname -a', or checking /etc/version file).
    Affected if The SDK version is exactly 3.4.11 or the firmware version is rer4_a_v3411b_2t2r_lev_09_170623.
  2. Confirm the boa web server is running
    Check if the boa web server process is active on the device. On embedded devices, this can be done via 'ps | grep boa' if shell access is available, or by accessing the device's web interface on port 80 or 443.
    Affected if The boa web server is running and accessible.
  3. Verify WSC web interface functionality is enabled
    Access the device's web admin interface and check the Wi-Fi Simple Config (WSC) settings page. Look for WSC/Wi-Fi Protected Setup configuration options in the wireless or advanced settings section. If you have CLI access, check configuration files or nvram settings for WSC-related parameters (e.g., 'wsc_enable', 'wps_enable').
    Affected if WSC (Wi-Fi Simple Config) web interface functionality is enabled on the device.
  4. Test for formWsc endpoint accessibility
    Send an HTTP GET request to the device's web interface and look for WSC-related form handlers. The vulnerable endpoint is typically /formWsc or similar WSC configuration paths. You can attempt: curl http://<device-ip>/formWsc or check the HTML source of WSC pages for form action URLs.
    Affected if The formWsc handler is accessible and responds to HTTP requests.

Your environment is affected if you are running Realtek rtl819x Jungle SDK v3.4.11 or Level1 WBR 6013 firmware rer4_a_v3411b_2t2r_lev_09_170623, the boa web server is active, and WSC web interface functionality is enabled, which exposes the vulnerable formWsc handler.

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

Apply any available vendor firmware updates for affected Realtek-based devices. If no update exists, consider disabling the WSC (Wi-Fi Simple Config) web interface functionality or implementing input length validation on the formWsc handler.

Fix this in Rtl819x Jungle Software Development Kit Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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