# CVE-2022-37953: WorkstationST - Response Splitting in AM Gateway Challenge-Response


- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Aug 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pjgf-vwqm-hxw7

## What is CVE-2022-37953?

CVE-2022-37953 is a medium-severity vulnerability in GE Gas Power WorkstationST, published on 25 Aug 2022. 

### Official description

An 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.

Weakness: CWE-113 (Improper Neutralization of CRLF Sequences in HTTP Headers)

## Which versions are affected by CVE-2022-37953?

It affects 1 product.


Products: Ge Workstationst.

## How do I fix CVE-2022-37953?

No fix has been published for CVE-2022-37953 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-37953 being exploited?

There is no known exploitation of CVE-2022-37953 in the wild and no public exploit code.

## Other vulnerabilities in GE Gas Power WorkstationST

- [CVE-2022-37952](https://insights.sbomify.com/CVE-2022-37952/): WorkstationST - Reflected XSS in iHistorian Data Display Tags (medium 4.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-37953 and fix it if it is affected.

What it is: CVE-2022-37953 is a medium-severity vulnerability in GE Gas Power WorkstationST, published on 25 Aug 2022. 
Exploitation: There is no known exploitation of CVE-2022-37953 in the wild and no public exploit code.

Affected product: GE Gas Power WorkstationST. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-37953/ (Markdown: https://insights.sbomify.com/CVE-2022-37953/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-37953
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-37953
- OSV: https://osv.dev/vulnerability/CVE-2022-37953

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-37953/
Summaries are generated and may contain mistakes; the official description above is the record.