CVE-2023-50330
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 · uneditedA stack-based buffer overflow vulnerability exists in the boa getInfo 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 · high confidenceA stack-based buffer overflow vulnerability exists in the boa web server's getInfo functionality within the Realtek rtl819x Jungle SDK v3.4.11. The vulnerability is triggered by sending a specially crafted series of HTTP requests that overflow a stack buffer in the getInfo handler, allowing an attacker to overwrite return addresses and achieve remote code execution.
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= 3.4.11= rer4_a_v3411b_2t2r_lev_09_170623CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the firmware versionAccess the device admin interface or check the firmware image file. For Level1 WBR-6013, look for the version string 'rer4_a_v3411b_2t2r_lev_09_170623' or similar 3.4.11 variants in the system information page or boot logs.Affected if The firmware version matches exactly 3.4.11 for the Realtek rtl819x Jungle SDK or 'rer4_a_v3411b_2t2r_lev_09_170623' for Level1 WBR-6013.
-
Confirm boa web server is runningIdentify if the boa HTTP server process is active on the device. This may require SSH/telnet access to the device's underlying Linux system or checking open ports (typically HTTP on port 80 or 443).Affected if The boa web server process is running and listening on network ports.
-
Check if getInfo functionality is exposedSend an HTTP request to the device targeting the getInfo handler endpoint. The exact URI path may vary but typically involves a query or form submission to the getInfo function within the boa server's CGI or form handling.Affected if The device responds to HTTP requests that trigger the getInfo functionality, indicating this handler is enabled and accessible.
-
Verify network accessibility of the web interfaceDetermine if the boa web server management interface is exposed to the network (not localhost-only or behind proper access controls). Check if the device's HTTP port is reachable from untrusted networks.Affected if The web interface is accessible from network segments where potential attackers could reach it.
A device is affected if it runs the Realtek rtl819x Jungle SDK version 3.4.11 (or the specific Level1 WBR-6013 firmware) with the boa web server and its getInfo functionality exposed to network attackers.
Generated from the published advisory. Verify against your own configuration.
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 dataApply any vendor firmware updates that patch this vulnerability in the affected Realtek rtl819x devices. If no update is available, consider network segmentation to limit exposure to the boa web server interface, or disable the getInfo functionality if possible.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50330 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-50330 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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