# CVE-2024-53354: SQL injection in n/a

> Remote authenticated attackers can execute arbitrary SQL commands via multiple API parameters in EasyVirt DCScope and CO2Scope.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jan 2025
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-xf5v-53c5-gf52

## What is CVE-2024-53354?

CVE-2024-53354 is a medium-severity SQL injection vulnerability in n/a, published on 31 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in EasyVirt DCScope <= 8.6.0 and CO2Scope <= 1.3.0 allows remote authenticated attackers to execute arbitrary SQL commands via the (1) user parameter to /api/management/findfilterlist; the (2) user or (3) filter parameter to /api/audit/findmetawatcher; the (4) user parameter to /api/audit/findmetaalert; the (5) user parameter to /api/management/ds; the (6) user or (7) filter parameter to /api/audit/findmetarunalert; the (7) user parameter to /api/management/findtimeview; the (8) user, (9) filter or (10) target parameter to /api/management/getihmsettings; the (11) user or (12) filter parameter to /api/management/elementstype; the (14) login, (15) user, (16) is_local, (17) is_ldap, or (18) is_openid parameter to /api/user/addalias; the (19) role parameter to /api/user/addrole; the (20) user or (21) filter parameter to /api/management/addtimeview; the (22) TIMEAGO, (23) IDENTIFIER, (24) USER, (25) NAME, or (26) COST parameter to /api/management/addtagcosts; the (27) USER, or (28) VM_COST parameter to /api/management/updategenericcpucost; the (29) VM, (30) HOST, or (31) STORAGE parameter to /api/management/updatecostinfo; the (32) user, (33) filter, or (34) timeago parameter to /api/management/addfilter; the (35) user parameter to /api/report/getreporthistory.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-53354?

It affects 2 products.


Products: Easyvirt Co2scope, Easyvirt Dcscope.

## How do I fix CVE-2024-53354?

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

## Is CVE-2024-53354 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-53356](https://insights.sbomify.com/CVE-2024-53356/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2024-55062](https://insights.sbomify.com/CVE-2024-55062/): Code injection in n/a (critical 9.8)
- [CVE-2024-57587](https://insights.sbomify.com/CVE-2024-57587/): SQL injection in n/a (critical 9.1)
- [CVE-2024-53355](https://insights.sbomify.com/CVE-2024-53355/): Missing authorization in n/a (high 8.8)
- [CVE-2024-53357](https://insights.sbomify.com/CVE-2024-53357/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53354 and fix it if it is affected.

What it is: CVE-2024-53354 is a medium-severity SQL injection vulnerability in n/a, published on 31 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-53354 in the wild and no public exploit code.

Affected product: n/a. 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-2024-53354/ (Markdown: https://insights.sbomify.com/CVE-2024-53354/index.md)
```

## Sources

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

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