CVE-2022-43184
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 · uneditedD-Link DIR878 1.30B08 Hotfix_04 was discovered to contain a command injection vulnerability via the component /bin/proc.cgi.
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 confidenceA command injection vulnerability exists in the /bin/proc.cgi component of D-Link DIR878 router firmware version 1.30B08 Hotfix_04, allowing remote attackers to inject and execute arbitrary operating system commands on the affected device.
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= 1.30b08CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 device modelCheck the device label or log into the router web interface and look for the model number in the status or system information pageAffected if The device is not a D-Link DIR878 router, then it is not affected by this specific CVE
-
Check the firmware versionLog into the router web interface and navigate to Status or System Information page to find the firmware version, or use the command 'cat /proc/firmware_version' via telnet/ssh if availableAffected if The firmware version is exactly 1.30B08 or 1.30b08 - other versions are not affected by this specific CVE
-
Verify the proc.cgi component existsAttempt to access the CGI component by sending an HTTP request to /cgi-bin/proc.cgi or /proc.cgi on the router's web interfaceAffected if The proc.cgi file exists and responds to HTTP requests, indicating the vulnerable component is present and accessible
-
Confirm web interface accessibilityAttempt to reach the router's IP address on HTTP/HTTPS ports (typically 80/443) from the networkAffected if The router web interface is accessible from the network, meaning the command injection vector is exposed to potential attackers
The device is affected only if it is a D-Link DIR878 router running firmware version 1.30B08 with the proc.cgi web interface accessible on the network.
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.
dbcve · scopedApply available firmware updates from D-Link; if no patch exists, restrict network access to the device and disable unauthenticated web interfaces.
DIR-878 latest firmware version (check support.dlink.com for the most recent release)
- 1. Visit the official D-Link support website at support.dlink.com
- 2. Search for DIR-878 router support page
- 3. Download the latest available firmware version for DIR-878
- 4. Access the router's web management interface (typically http://192.168.0.1)
- 5. Navigate to the Firmware Upgrade or System section
- 6. Upload and install the downloaded firmware file
- 7. Wait for the upgrade to complete and the router to reboot
- 8. Verify the new firmware version is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43184 — 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-2022-43184 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