CVE-2022-32284
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 · uneditedUse of insufficiently random values vulnerability exists in Vnet/IP communication module VI461 of YOKOGAWA Wide Area Communication Router (WAC Router) AW810D, which may allow a remote attacker to cause denial-of-service (DoS) condition by sending a specially crafted packet.
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 confidenceInsufficiently random values in the Vnet/IP communication module VI461 of the AW810D Wide Area Communication Router allow a remote attacker to cause denial-of-service by sending specially crafted packets. The vulnerability stems from predictable or weak random number generation used in the protocol, potentially allowing an attacker to infer or manipulate communication sequences.
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<= r12CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Confirm AW810D model identificationLocate the device model identifier in the system information, hardware label, or management interface - verify the device is specifically an AW810D Wide Area Communication RouterAffected if The device model is not AW810D (different models are not affected by this specific CVE)
-
Check firmware version against affected rangeAccess the firmware version information through the device management interface, CLI, or system diagnostics. Compare the installed version to the r12 baseline - versions r12 and earlier are within the affected rangeAffected if Firmware version is r12 or earlier (r1 through r12)
-
Verify Vnet/IP module VI461 is configuredLocate the module or feature configuration for Vnet/IP communication (may be listed as VI461 or Vnet/IP in the module list, protocol settings, or communication interface configuration)Affected if The Vnet/IP module VI461 is present and enabled in the configuration
-
Assess network accessibility of the Vnet/IP serviceReview network exposure settings, firewall rules, or interface bindings for the Vnet/IP communication module to determine if it listens on accessible network interfacesAffected if The Vnet/IP module is bound to network interfaces reachable from untrusted networks
A user is affected if the device is an AW810D router running firmware r12 or earlier with the Vnet/IP module VI461 enabled and accessible from the network where crafted packets could be received.
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 vendor patches for the AW810D firmware addressing random value generation in the Vnet/IP module. If no patch is available, implement network segmentation and firewall rules to limit exposure to untrusted network sources reaching the affected module.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32284 — 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-32284 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