CVE-2022-2337
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 · uneditedA crafted HTTP packet with a missing HTTP URI can create a denial-of-service condition in Softing Secure Integration Server V1.22.
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 denial-of-service vulnerability exists in Softing Secure Integration Server V1.22 where the server fails to properly handle HTTP requests lacking a URI component. When the server processes a specially crafted HTTP packet with a missing URI, it enters a denial-of-service condition, potentially making the service unavailable.
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= 3.1= 3.1= 5.2= 6= 1.22= 1.74CVSS 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 Softing productLocate Softing Secure Integration Server, Edgeaggregator, Edgeconnector, OPC, UAGates, or OPC UA C++ SDK installations on the system. Check installed programs, services, or application directories for Softing components.Affected if Any Softing product from the affected list is installed on the system.
-
Determine installed versionAccess the product's version information through its UI, service properties, or check the binary/dll version properties. For Secure Integration Server, verify the exact version number.Affected if The installed version matches exactly: Secure Integration Server 1.22, Edgeaggregator 3.1, Edgeconnector 3.1, OPC 5.2, OPC UA C++ SDK 6, or UAGates 1.74.
-
Verify HTTP service is exposedConfirm the Softing service exposes an HTTP interface. Check network listeners, firewall rules, or service configuration for HTTP port availability (common ports: 80, 443, 8080, 8443).Affected if The product runs an HTTP service that accepts external or internal HTTP connections.
-
Test HTTP request handlingSend a raw HTTP request without a URI component (for example: 'GET / HTTP/1.1\r\nHost: target\r\n\r\n' with the '/' and path removed) to the service endpoint and observe the response or service availability.Affected if The service becomes unresponsive, crashes, or fails to properly respond after receiving an HTTP request with a missing URI component.
-
Check service stabilityMonitor the Softing service process for unexpected termination or inability to accept new connections after processing malformed HTTP traffic.Affected if The service enters a denial-of-service condition and cannot recover without restart.
The environment is affected if a Softing product version 1.22 (Secure Integration Server), 3.1 (Edgeaggregator/Edgeconnector), 5.2 (OPC), 6 (OPC UA C++ SDK), or 1.74 (UAGates) is installed with an exposed HTTP interface that fails when processing requests lacking a URI component.
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 available patches or updates from Softing for Secure Integration Server V1.22. Until a patch is available, consider implementing network-level filtering to block malformed HTTP requests or deploying the server behind a reverse proxy that validates HTTP request structure.
- Consultation3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2337 — 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-2337 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