# CVE-2012-5937: Command injection in n/a

> Remote attackers can execute arbitrary commands on IBM Sterling Integrator servers via unspecified vectors in the CLA2 server.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3x98-xr5x-2c7r

## What is CVE-2012-5937?

CVE-2012-5937 is a critical command injection vulnerability in Ibm Sterling B2b Integrator, published on 12 Apr 2013. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the CLA2 server in IBM Gentran Integration Suite 4.3, Sterling Integrator 5.0 and 5.1, and Sterling B2B Integrator 5.2, as used in IBM Sterling File Gateway 1.1 through 2.2 and other products, allows remote attackers to execute arbitrary commands via unknown vectors.

## Which versions are affected by CVE-2012-5937?

It affects 4 products.


Products: Ibm Gentran Integration Suite, Ibm Sterling B2b Integrator, Ibm Sterling File Gateway, Ibm Sterling Integrator.

## How do I fix CVE-2012-5937?

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

## Is CVE-2012-5937 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5937 and fix it if it is affected.

What it is: CVE-2012-5937 is a critical command injection vulnerability in Ibm Sterling B2b Integrator, published on 12 Apr 2013. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-5937 in the wild and no public exploit code.

Affected product: Ibm Sterling B2b Integrator. 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-2012-5937/ (Markdown: https://insights.sbomify.com/CVE-2012-5937/index.md)
```

## Sources

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

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