CVE-2022-42787
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 W&T products of the Comserver Series use a small number space for allocating sessions ids. After login of an user an unathenticated remote attacker can brute force the users session id and get access to his account on the the device. As the user needs to log in for the attack to be successful a user interaction is required.
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 confidenceSession hijacking vulnerability in W&T Comserver Series devices where the session ID uses a small number space, allowing unauthenticated remote attackers to brute-force valid session IDs after a user logs in and take over the user's session.
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.48< 1.48< 1.48< 1.76< 1.76< 1.76< 1.76< 1.76CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 device modelAccess the device's web interface, console, or device label to determine the exact model (e.g., Com Server ++, Com Server 20ma, Com Server Highspeed 100basefx, etc.)Affected if The device is any W&T Comserver model from the affected product list
-
Determine the installed firmware versionCheck the device's web interface (typically under System, Status, or About section), or use the device's command-line interface or management console to retrieve the firmware versionAffected if The firmware version cannot be determined or is older than the patched version
-
Compare firmware version against affected rangesFor Com Server ++, Com Server 20ma, and At Modem Emulator: check if version is below 1.48. For Com Server Highspeed models (100basefx, 100baselx, 19inch 1port, 19inch 4port, Compact): check if version is below 1.76Affected if The firmware version is below 1.48 for non-Highspeed models, or below 1.76 for Highspeed models
-
Verify session handling configuration (if accessible)If the device management interface exposes session configuration or logs, check for any settings related to session timeout, session ID generation, or active session monitoringAffected if Session configuration is exposed and shows non-standard or weak session management settings (note: direct testing of session ID entropy is not recommended as it constitutes active exploitation)
-
Review authentication logs for suspicious session activityExamine device logs, if available, for multiple failed session authentication attempts or unexpected session creation patterns that may indicate brute-force activityAffected if Logs show anomalous session activity patterns or evidence of session hijacking attempts
The environment is likely affected if the device is a W&T Comserver model running firmware version below 1.48 (for At Modem Emulator, Com Server ++, Com Server 20ma) or below 1.76 (for Com Server Highspeed variants).
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.481.76
Vendor must implement cryptographically secure session ID generation with sufficient entropy. Users should monitor sessions and log out when finished, awaiting vendor firmware update.
Modem Emulator: >=1.48 | Com Server ++: >=1.48 | Com Server 20ma: >=1.48 | Com Server Highspeed (all variants): >=1.76
- 1. Identify the specific W&T Com Server or Modem Emulator device model from the affected product list
- 2. Determine the current firmware version installed on the device through the web interface or administration panel
- 3. Download the latest firmware from the official W&T website (wuerttemberg-elektronik.de) or through the vendor's support channels
- 4. Back up the current device configuration if possible
- 5. Access the device administration interface and navigate to the firmware upgrade section
- 6. Upload and apply the new firmware: version 1.48 or higher for Modem Emulator/Com Server/Com Server ++/Com Server 20ma; version 1.76 or higher for all Com Server Highspeed variants
- 7. Verify the firmware upgrade was successful and the device is operational
- 8. Confirm the new firmware version is displayed correctly in the device status
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42787 — 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-42787 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