# CVE-2007-4152: Other in n/a

> Remote attackers can replay captured session data to manipulate audit scheduling in Visionsoft Audit.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 3 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j5hf-f8j5-h5qm

## What is CVE-2007-4152?

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

### Official description

The Visionsoft Audit on Demand Service (VSAOD) in Visionsoft Audit 12.4.0.0 allows remote attackers to conduct replay attacks by capturing and resending data from the DETAILS and PROCESS sections of a session that schedules an audit.

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

It affects 1 product.


Products: Visionsoft Audit.

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

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

## Is CVE-2007-4152 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4148](https://insights.sbomify.com/CVE-2007-4148/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-4149](https://insights.sbomify.com/CVE-2007-4149/): Missing authorization in n/a (critical 10.0)
- [CVE-2007-4150](https://insights.sbomify.com/CVE-2007-4150/): Weak cryptography in n/a (high 7.5)
- [CVE-2007-4151](https://insights.sbomify.com/CVE-2007-4151/): Information disclosure in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4152 is a critical vulnerability in n/a, published on 3 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-4152 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-4152/ (Markdown: https://insights.sbomify.com/CVE-2007-4152/index.md)
```

## Sources

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

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