CVE-2022-4098
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 · uneditedMultiple Wiesemann&Theis products of the ComServer Series are prone to an authentication bypass through IP spoofing. After a user logged in to the WBM of the Com-Server an unauthenticated attacker in the same subnet can obtain the session ID and through IP spoofing change arbitrary settings by crafting modified HTTP Get requests. This may result in a complete takeover of the device.
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 · high confidenceThe ComServer Series web-based management (WBM) uses IP-based session validation, allowing an unauthenticated attacker on the same subnet to obtain a valid session ID and then spoof the legitimate user's IP address to send crafted HTTP GET requests with that session, achieving arbitrary setting changes and complete device takeover.
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.55< 1.55< 1.78< 1.78< 1.78< 1.78< 1.78< 1.78CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/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 the ComServer model and firmware versionAccess the WBM web interface by entering the device IP in a browser. The firmware version is typically displayed on the login page or in the 'System Info' or 'Status' section of the web interface. Alternatively, check the device label or documentation.Affected if The device is a Wut Com Server model and the displayed firmware version is below 1.55 (for Com Server ++ or 20ma) or below 1.78 (for Highspeed variants).
-
Confirm WBM web interface is enabledAttempt to access the device by entering its IP address in a web browser. If a login page or device status page loads, the WBM interface is active.Affected if The WBM web interface is accessible over HTTP/HTTPS on the network.
-
Determine network accessibility to the deviceCheck whether the device IP is reachable from network segments that contain untrusted or unauthorized users. Use 'ipconfig' or 'ifconfig' to identify your subnet, then ping the device IP to confirm reachability.Affected if The device is on a subnet that includes or may include unauthenticated users, or the device is exposed to networks beyond the trusted internal network.
If the device is a Wut Com Server with firmware below 1.55 (or 1.78 for Highspeed models) AND the WBM interface is network-accessible, the environment is vulnerable to IP-spoofing session hijacking as described in CVE-2022-4098.
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.
dbcve · scoped1.551.78
Implement network segmentation to isolate affected devices from untrusted users, and contact vendor for firmware updates that implement proper session binding beyond IP address. If no patch available, consider compensating controls such as restricting network access via ACLs.
Com Server ++ and 20ma: firmware >= 1.55; Com Server Highspeed variants: firmware >= 1.78
- 1. Identify the exact Com Server model in your deployment from the affected product list
- 2. Determine the current firmware version by accessing the device's web-based management (WBM) interface or using the manufacturer's discovery tool
- 3. Download the appropriate firmware version from the Wiesemann&Theis support portal or authorized distributor: For Com Server ++ and Com Server 20ma, download firmware version 1.55 or later; For all Com Server Highspeed variants, download firmware version 1.78 or later
- 4. Consult the device manual for firmware update instructions, typically involving uploading the .bin file through the WBM interface under 'Maintenance' or ' firmware update' section
- 5. Verify the firmware upgrade was successful by checking the new version in the WBM
- 6. After upgrade, monitor for any unexpected behavior and consider reviewing access control policies to restrict network access to trusted subnets only
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4098 — 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-4098 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