# CVE-2022-48475: Memory corruption in Control de Ciber

> A buffer overflow in Control de Ciber allows attackers to cause denial of service or execute code when an administrator processes a malicious print query.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Sep 2023
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-cj96-qrcp-8ffp

## What is CVE-2022-48475?

CVE-2022-48475 is a high-severity memory corruption vulnerability in Control de Ciber, published on 12 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer Overflow vulnerability in Control de Ciber version 1.650, in the printing function. Sending a modified request by the attacker could cause a Buffer Overflow when the adminitrator tries to accept or delete the print query created by the request.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Cbm Control De Ciber.

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

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

## Is CVE-2022-48475 being exploited?

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

## Other vulnerabilities in Control de Ciber

- [CVE-2022-48474](https://insights.sbomify.com/CVE-2022-48474/): Denial of service in Control de Ciber (high 8.2)
- [CVE-2022-4896](https://insights.sbomify.com/CVE-2022-4896/): Denial of service in Control de Ciber (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-48475 is a high-severity memory corruption vulnerability in Control de Ciber, published on 12 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-48475 in the wild and no public exploit code.

Affected product: Control de Ciber. 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-48475/ (Markdown: https://insights.sbomify.com/CVE-2022-48475/index.md)
```

## Sources

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

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