CVE-2022-1737
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 · uneditedPyramid Solutions' affected products, the Developer and DLL kits for EtherNet/IP Adapter and EtherNet/IP Scanner, are vulnerable to an out-of-bounds write, which may allow an unauthorized attacker to send a specially crafted packet that may result in a denial-of-service condition.
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 confidenceOut-of-bounds write vulnerability in Pyramid Solutions' Developer and DLL kits for EtherNet/IP Adapter and EtherNet/IP Scanner allows unauthenticated attackers to send specially crafted packets causing a denial-of-service condition.
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<= 4.4.0<= 4.4.0<= 4.4.0<= 4.4.0CVSS 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.
-
Identify installed Pyramid Solutions softwareCheck your system for installed Pyramid Solutions Netstax Ethernet/IP Adapter or Scanner software (Development Kit or DLL Kit). Look in program directories, installed programs list, or check for related DLL files and components.Affected if Any of the four affected products (Netstax Ethernet/IP Adapter Development Kit, Adapter DLL Kit, Scanner Development Kit, or Scanner DLL Kit) are found on the system
-
Determine installed versionLocate the version information for the installed Pyramid Solutions software. Check the software's about dialog, version properties of executable/DLL files, or check installed program details.Affected if The installed version is 4.4.0 or lower
-
Verify software is active or network-exposedDetermine if the affected Pyramid Solutions software is running as a service or process, or if network ports/protocols related to EtherNet/IP communication are active and accessible from the network.Affected if The software is running and accessible on the network, making it vulnerable to specially crafted packets
-
Check for network exposureReview firewall rules and network configuration to determine if the EtherNet/IP services are exposed to untrusted networks or accessible from external systems.Affected if The affected software can receive packets from untrusted or external network sources
A system is affected if it has any Pyramid Solutions Netstax Ethernet/IP Adapter or Scanner kit (Development or DLL) version 4.4.0 or lower installed and running, with the service exposed to network traffic.
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 when available; until then, isolate affected systems behind firewalls or network segmentation to limit exposure to untrusted network traffic.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1737 — 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-1737 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