# CVE-2022-32512: A CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability exists that could cause remote code executi


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Jan 2023
- **Updated:** 5 Feb 2025
- **Also known as:** GHSA-grhm-x47f-j3jc

## What is CVE-2022-32512?

CVE-2022-32512 is a medium-severity vulnerability in Schneider Electric CanBRASS, published on 30 Jan 2023. 

### Official description

A CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability exists that could cause remote code execution when a command which exploits this vulnerability is utilized. Affected Products: CanBRASS (Versions prior to V7.5.1)

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Schneider-Electric Canbrass.

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

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

## Is CVE-2022-32512 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-32512 is a medium-severity vulnerability in Schneider Electric CanBRASS, published on 30 Jan 2023. 
Exploitation: There is no known exploitation of CVE-2022-32512 in the wild and no public exploit code.

Affected product: Schneider Electric CanBRASS. 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-32512/ (Markdown: https://insights.sbomify.com/CVE-2022-32512/index.md)
```

## Sources

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

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