CVE-2022-2547
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 without a content-type header 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 crafted HTTP packet without a content-type header can trigger a denial-of-service condition in Softing Secure Integration Server V1.22, likely due to improper input validation or null pointer handling when the header is absent or improperly processed.
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 software on the system by checking installed programs, running services, or common installation directories (e.g., C:\Program Files\Softing or /opt/softing). Identify which Softing product is present (Edgeaggregator, Edgeconnector, OPC, OPC UA C++ SDK, Secure Integration Server, or Uagates).Affected if Any of the listed Softing products (Edgeaggregator, Edgeconnector, OPC, OPC UA C++ SDK, Secure Integration Server, or Uagates) is installed.
-
Check installed version against affected versionsDetermine the exact version of the installed Softing product using the vendor's documentation, software UI, or system registry (Windows) / package manager (Linux). Compare the installed version to the affected versions: Edgeaggregator = 3.1, Edgeconnector = 3.1, OPC = 5.2, OPC UA C++ SDK = 6, Secure Integration Server = 1.22, Uagates = 1.74.Affected if The installed version exactly matches 3.1 (Edgeaggregator/Edgeconnector), 5.2 (OPC), 6 (OPC UA C++ SDK), 1.22 (Secure Integration Server), or 1.74 (Uagates).
-
Verify HTTP interface is accessibleDetermine if the HTTP service of the Softing product is exposed by checking network listener configurations, firewall rules, or by attempting to access the HTTP endpoint (e.g., curl http://localhost:<port> or curl http://<hostname>:<port> if externally accessible).Affected if The HTTP interface of the Softing product is listening and accessible on any network interface.
-
Test for vulnerable header handlingSend a crafted HTTP request WITHOUT a Content-Type header to the exposed HTTP endpoint (e.g., curl -X POST -d 'test' http://<host>:<port>/<endpoint>). Observe if the service becomes unresponsive, crashes, or returns an error indicating a null pointer or processing failure.Affected if The service becomes unresponsive or crashes when receiving an HTTP request without a Content-Type header.
A user is affected if they have any of the listed Softing products installed with a version matching exactly 3.1, 5.2, 6, 1.22, or 1.74, and the HTTP interface is accessible and exhibits denial-of-service behavior when receiving requests without Content-Type headers.
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; otherwise, deploy a reverse proxy or WAF in front of the server to validate that HTTP requests include proper headers before forwarding to the application.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2547 — 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-2547 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