dbcve.org
Rtl819x Software Development KitApplication · Realtek

CVE-2022-29558

HIGH · 8.8 CVSS v3.1 Published 2022-07-28
Fix available
A fix is available. Upgrade to 3.6.1 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Realtek rtl819x-SDK before v3.6.1 allows command injection over the web interface.

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

Command injection vulnerability in the web interface of Realtek rtl819x-SDK versions prior to 3.6.1 allows remote attackers to execute arbitrary system commands via crafted HTTP requests to the web management interface.

MitigationUpgrade to Realtek rtl819x-SDK v3.6.1 or later, or apply vendor-provided firmware updates for devices that embed this SDK.

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 Software Development KitApplication
Affected:< 3.6.1

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

CVSS:3.1/AV:N/AC:L/PR:L/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 if the device uses Realtek rtl819x SDK
    Check product documentation, firmware metadata, or examine the firmware image for Realtek rtl819x components. Look for strings or files referencing 'rtl819x' or 'Realtek' SDK in the system.
    Affected if The device or firmware is confirmed to be based on the Realtek rtl819x Software Development Kit.
  2. Determine the installed SDK version
    Locate version information within the firmware, device system files, or web interface footer/admin pages. Check for files or strings containing 'rtl819x' along with version numbers (e.g., in /etc/*, /var/, or embedded in web server binaries).
    Affected if The identified version is lower than 3.6.1 (e.g., 3.5.x, 3.0.x, or any version number without a patch that includes 3.6.1 or later).
  3. Verify the web management interface is accessible
    Attempt to access the device's web interface via HTTP/HTTPS on common management ports (typically 80, 443, 8080). Confirm the web server is running and responding to requests.
    Affected if The web management interface is active and reachable on the network.
  4. Check for vulnerable HTTP handling components
    If you have access to the firmware, examine the web server binaries or CGI scripts for command handling functions that process user input from HTTP requests. Look for instances where web request parameters are passed to system() or similar execution functions without proper sanitization.
    Affected if The web interface processes HTTP request parameters in a manner consistent with command injection (unfiltered input passed to shell execution functions), and the SDK version is below 3.6.1.

The environment is affected if the device or firmware uses the Realtek rtl819x SDK at a version lower than 3.6.1 and has the web management interface enabled, allowing remote attackers to inject commands through crafted HTTP requests.

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.

dbcve · scoped
Upgrade available Upgrade to 3.6.1 or later
Fixed in 3.6.1
Interim mitigation

Upgrade to Realtek rtl819x-SDK v3.6.1 or later, or apply vendor-provided firmware updates for devices that embed this SDK.

Recommended fix Moderate confidence

Rtl819x SDK v3.6.1

  1. 1. Identify all products and firmware images that incorporate the Realtek rtl819x-SDK versions prior to v3.6.1
  2. 2. Obtain the fixed rtl819x-SDK v3.6.1 or later from the official Realtek website or distribution channel
  3. 3. Replace the vulnerable SDK library files in the product firmware build system with the fixed version
  4. 4. Rebuild the firmware image incorporating the patched SDK
  5. 5. Deploy the updated firmware to all affected devices
  6. 6. Verify that the command injection vulnerability is no longer present through security testing

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rtl819x Software Development Kit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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