# CVE-2010-4773: Other in n/a

> Remote attackers can execute arbitrary code on Hitachi EUR Form Client and Service products via unspecified vectors.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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 stated
- **Fix available:** No
- **Published:** 23 Mar 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h8wq-82x5-99wg

## What is CVE-2010-4773?

CVE-2010-4773 is a critical vulnerability in n/a, published on 23 Mar 2011. It can be exploited over the network.

### Official description

Unspecified vulnerability in Hitachi EUR Form Client before 05-10 -/D 2010.11.15 and 05-10-CA (* 2) 2010.11.15; Hitachi EUR Form Service before 05-10 -/D 2010.11.15; and uCosminexus EUR Form Service before 07-60 -/D 2010.11.15 on Windows, before 05-10 -/D 2010.11.15 and 07-50 -/D 2010.11.15 on Linux, and before 07-50 -/C 2010.11.15 on AIX; allows remote attackers to execute arbitrary code via unknown attack vectors.

## Which versions are affected by CVE-2010-4773?

It affects 3 products.


Products: Hitachi Eur Form Client, Hitachi Eur Form Service, Hitachi Ucosminexus Eur Form Service.

## How do I fix CVE-2010-4773?

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

## Is CVE-2010-4773 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-4773 and fix it if it is affected.

What it is: CVE-2010-4773 is a critical vulnerability in n/a, published on 23 Mar 2011. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2010-4773 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-2010-4773/ (Markdown: https://insights.sbomify.com/CVE-2010-4773/index.md)
```

## Sources

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

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