# CVE-2007-4123: Information disclosure in n/a

> Attackers can obtain sensitive schedule configuration data from Hitachi Groupmax Groupware Server due to improper data management.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 1 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4754-4495-xmhp

## What is CVE-2007-4123?

CVE-2007-4123 is a medium-severity vulnerability in n/a, published on 1 Aug 2007. It can be exploited over the network.

### Official description

The Groupmax Scheduler_Facilities management tool in Hitachi Groupmax Groupware Server 07-00-/F through 07-32-/A before 20070731 does not properly manage schedule server configuration data, which might allow attackers to obtain sensitive information via unspecified vectors.

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

It affects 1 product.


Products: Hitachi Groupmax Groupware Server.

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

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

## Is CVE-2007-4123 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-3172](https://insights.sbomify.com/CVE-2009-3172/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4123 is a medium-severity vulnerability in n/a, published on 1 Aug 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2007-4123 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-4123/ (Markdown: https://insights.sbomify.com/CVE-2007-4123/index.md)
```

## Sources

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

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