CVE-2022-46562
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 DIR-882 DIR882A1_FW130B06, DIR-878 DIR_878_FW1.30B08 was discovered to contain a stack overflow via the PSK parameter in the SetQuickVPNSettings module.
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 confidenceStack-based buffer overflow in D-Link DIR-882 and DIR-878 routers. The vulnerability exists in the SetQuickVPNSettings module where the PSK (Pre-Shared Key) parameter is not properly bounds-checked before being copied to a stack buffer, allowing authenticated attackers to overwrite return addresses and potentially execute arbitrary code.
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.30b06CVSS 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 router modelCheck the device label or web interface status page to confirm the router is a D-Link DIR-882 or DIR-878 modelAffected if Router model is DIR-882 A1 or DIR-878 within the affected product range
-
Check firmware versionAccess the router web interface (typically at 192.168.0.1), navigate to Status or Management section, and verify the firmware version. For DIR-882 A1, the affected version is 1.30b06Affected if Firmware version matches 1.30b06 on DIR-882 A1
-
Verify QuickVPN functionality is accessibleLog into the router web interface and navigate to the VPN or QuickVPN settings section. Check if the SetQuickVPNSettings module is present and configurableAffected if QuickVPN settings interface is available and the PSK parameter can be configured
-
Confirm administrative access to routerVerify you have web-based administrative access to the router. This vulnerability requires an authenticated attacker, so confirm whether remote management is enabled and accessibleAffected if Administrative web interface is accessible (either locally or remotely if remote management is enabled)
You are affected if you own a D-Link DIR-882 A1 or DIR-878 router running firmware version 1.30b06 with QuickVPN feature accessible to authenticated users
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 dataSince no firmware patch is available, implement compensating controls: restrict admin interface access to trusted IPs via firewall, disable QuickVPN if unused, and monitor for indicators of compromise. Consider replacing affected hardware with supported alternatives.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46562 — 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-46562 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