# CVE-2007-4204: Business logic in n/a

> Authenticated users can access sensitive schedule data belonging to other users due to incorrect data assignment logic.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:P/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:** 8 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-crqw-2ww4-m54r

## What is CVE-2007-4204?

CVE-2007-4204 is a low-severity vulnerability in n/a, published on 8 Aug 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Hitachi Groupmax Collaboration - Schedule, as used in Groupmax Collaboration Portal 07-32 through 07-32-/B, uCosminexus Collaboration Portal 06-32 through 06-32-/B, and Groupmax Collaboration Web Client - Mail/Schedule 07-32 through 07-32-/A, can assign schedule data to the wrong user under unspecified conditions, which might allow remote authenticated users to obtain sensitive information.

## Which versions are affected by CVE-2007-4204?

It affects 3 products.


Products: Hitachi Groupmax Collaboration Portal, Hitachi Groupmax Collaboration Web Client, Hitachi Ucosminexus Collaboration Portal.

## How do I fix CVE-2007-4204?

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

## Is CVE-2007-4204 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-5808](https://insights.sbomify.com/CVE-2007-5808/): Information disclosure in n/a (medium 5.0)
- [CVE-2007-3043](https://insights.sbomify.com/CVE-2007-3043/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4204 and fix it if it is affected.

What it is: CVE-2007-4204 is a low-severity vulnerability in n/a, published on 8 Aug 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-4204 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-2007-4204/ (Markdown: https://insights.sbomify.com/CVE-2007-4204/index.md)
```

## Sources

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

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