dbcve.org
Rtl819x Jungle Software Development KitApplication · Realtek

CVE-2023-49073

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 formFilter functionality of Realtek rtl819x Jungle SDK v3.4.11. A specially crafted series of HTTP requests can lead to arbitrary code execution. An attacker can send a sequence of 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 · high confidence

A stack-based buffer overflow vulnerability exists in the boa web server's formFilter functionality within Realtek rtl819x Jungle SDK v3.4.11. The vulnerability allows specially crafted HTTP requests to overflow a stack-based buffer, potentially enabling arbitrary code execution on the affected device.

MitigationApply any vendor-supplied firmware patches for the rtl819x SDK. If no patch is available, restrict network access to the device's web interface and consider network segmentation to limit exposure.

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 version in use
    Check the device's firmware documentation, boot logs, or system information for the Realtek rtl819x Jungle SDK version. Look for strings like 'rtl819x' or 'Jungle SDK' in firmware files or device interfaces.
    Affected if The device is running Realtek rtl819x Jungle SDK version 3.4.11 exactly.
  2. Confirm the specific device model
    Identify if the device is a Level1 Wbr 6013 or any device using the affected Realtek rtl819x SDK. Check the device label, admin interface, or firmware metadata.
    Affected if The device is a Level1 Wbr 6013 running firmware version rer4_a_v3411b_2t2r_lev_09_170623.
  3. Verify the boa web server is active
    Check running processes on the device for the 'boa' web server binary. On embedded devices, this may require accessing the device via SSH, telnet, or serial console and running commands like 'ps' or checking /proc/processes.
    Affected if The boa web server process is running on the device.
  4. Check web interface accessibility
    Determine if the device's HTTP/HTTPS web management interface is exposed to untrusted networks. Review firewall rules, NAT configurations, or ACLs that control access to the device's web port (typically 80 or 443).
    Affected if The web interface is accessible from untrusted network segments or the internet.
  5. Inspect formFilter functionality
    If you have access to the device's web server configuration or source code, examine the formFilter handler in the boa web server for the vulnerability. This typically requires firmware extraction or access to the SDK source code.
    Affected if The formFilter functionality is present and accessible via HTTP requests to the device.

A device is affected if it runs the Realtek rtl819x Jungle SDK version 3.4.11 (or Level1 Wbr 6013 firmware rer4_a_v3411b) with the boa web server and its formFilter feature is accessible to an attacker.

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 vendor-supplied firmware patches for the rtl819x SDK. If no patch is available, restrict network access to the device's web interface and consider network segmentation to limit exposure.

Fix this in Rtl819x Jungle Software Development Kit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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