CVE-2022-37953
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 · uneditedAn HTTP response splitting vulnerability exists in the AM Gateway Challenge-Response dialog of WorkstationST (<v07.09.15) and could allow an attacker to compromise a victim's browser/session. WorkstationST is only deployed in specific, controlled environments rendering attack complexity significantly higher than if the attack were conducted on the software in isolation. WorkstationST v07.09.15 can be found in ControlST v07.09.07 SP8 and greater.
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 confidenceHTTP response splitting vulnerability in the AM Gateway Challenge-Response dialog of WorkstationST versions prior to v07.09.15 allows attackers to inject malicious headers or split HTTP responses to compromise victim browsers and sessions.
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< 07.09.15CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Confirm WorkstationST installationLocate the WorkstationST application on the system - check Program Files folder or look for workstationst.exe process runningAffected if WorkstationST is not installed on the system, the vulnerability does not apply
-
Identify installed versionRight-click on the WorkstationST executable or shortcut, select Properties, and check the version information in the Details tab. Alternatively, open WorkstationST and look for the version in the About or Help menuAffected if The version number is lower than 07.09.15, indicating an affected version
-
Verify AM Gateway component presenceCheck if the AM Gateway module is available in the WorkstationST installation by examining the installed components or modules within the application interfaceAffected if The AM Gateway Challenge-Response dialog feature exists in the installation and is accessible to users
-
Confirm network exposureDetermine if the WorkstationST web server or gateway interface is accessible over the network by checking the service configuration and listening portsAffected if the AM Gateway interface is exposed to network users who could exploit the HTTP response splitting flaw
The system is affected if WorkstationST is installed with a version lower than 07.09.15 and the AM Gateway Challenge-Response dialog feature is present and accessible.
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 · scoped07.09.15
Upgrade WorkstationST to v07.09.15 or later (also available in ControlST v07.09.07 SP8 and greater) to remediate this vulnerability.
WorkstationST v07.09.15 (or ControlST v07.09.07 SP8 and greater)
- 1. Identify the current version of WorkstationST or ControlST currently deployed
- 2. Obtain WorkstationST v07.09.15 or ControlST v07.09.07 SP8 or greater from GE's official distribution channels
- 3. Follow GE's standard upgrade procedure for WorkstationST or ControlST
- 4. After upgrade, verify the version is v07.09.15 or higher by checking the WorkstationST 'About' or version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37953 — 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-37953 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