dbcve.org
Rtl819x Jungle Software Development KitApplication · Realtek

CVE-2023-45215

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 setRepeaterSsid functionality of Realtek rtl819x Jungle SDK v3.4.11. A specially crafted series of network 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 exists in the boa web server's setRepeaterSsid function within Realtek's rtl819x Jungle SDK v3.4.11. The function fails to properly validate the length of SSID input before copying it to a fixed-size stack buffer, allowing an attacker to overwrite return addresses and execute arbitrary code via specially crafted network requests.

MitigationUpdate to a patched SDK version if available, or implement strict length validation on the SSID parameter in the setRepeaterSsid function before any memory copy operations, ensuring input does not exceed the destination buffer size.

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. Check the SDK or firmware version
    Identify the installed version of the Realtek rtl819x Jungle SDK or the Level1 WBR 6013 firmware. For firmware, check /etc/version, the kernel banner, or the web interface status page. For SDK-based products, check product documentation or firmware metadata.
    Affected if The version equals 3.4.11 for the Realtek SDK, or equals rer4_a_v3411b_2t2r_lev_09_170623 for Level1 WBR 6013 firmware.
  2. Verify the boa web server is running
    Check if the boa process is running on the device. Use 'ps | grep boa' or check open ports: 'netstat -tlnp | grep 80' or 'ss -tlnp | grep :80'. The boa server typically listens on HTTP port 80.
    Affected if The boa web server is active and serving HTTP requests.
  3. Confirm wireless repeater functionality is enabled
    Check if the device has wireless repeater or WDS (Wireless Distribution System) features configured. Look for interfaces like 'ra0', 'rai0', or 'wlan0' in the network configuration. Access the web interface and navigate to wireless settings to see if repeater/bridge modes are active.
    Affected if Wireless repeater, access point, or WDS mode is configured and the SSID can be set through the web interface.
  4. Inspect the setRepeaterSsid function availability
    If you have shell access, check the boa binary or web application for the setRepeaterSsid handler. Look in /usr/www or /www for CGI scripts or the boa binary itself: 'strings /usr/sbin/boa | grep -i repeater' or 'find / -name "boa*" 2>/dev/null'.
    Affected if The setRepeaterSsid function is present in the web server's CGI handlers or binary.

You are affected if your device runs the Realtek rtl819x Jungle SDK v3.4.11 or the Level1 WBR 6013 rer4_a_v3411b_2t2r_lev_09_170623 firmware, AND the boa web server is active with wireless repeater/SSID configuration capability exposed.

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

Update to a patched SDK version if available, or implement strict length validation on the SSID parameter in the setRepeaterSsid function before any memory copy operations, ensuring input does not exceed the destination buffer size.

Fix this in Rtl819x Jungle Software Development Kit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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