# CVE-2025-3361: HGiga iSherlock - OS Command Injection

> Unauthenticated remote attackers can inject and execute arbitrary OS commands on HGiga iSherlock servers via the web service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 8 Apr 2025
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-gh5j-5f8x-j85c

## What is CVE-2025-3361?

CVE-2025-3361 is a critical command injection vulnerability in HGiga iSherlock 4.5, published on 8 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web service of iSherlock from HGiga has an OS Command Injection vulnerability, allowing unauthenticated remote attackers to inject arbitrary OS commands and execute them on the server.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-3361?


## How do I fix CVE-2025-3361?

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

## Is CVE-2025-3361 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3361 and fix it if it is affected.

What it is: CVE-2025-3361 is a critical command injection vulnerability in HGiga iSherlock 4.5, published on 8 Apr 2025. 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-2025-3361 in the wild and no public exploit code.

Affected product: HGiga iSherlock 4.5. 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-2025-3361/ (Markdown: https://insights.sbomify.com/CVE-2025-3361/index.md)
```

## Sources

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

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