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

> Authenticated users can modify server data via flawed redirection logic in InterSystems Cache' CSP implementation.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:N/I:P/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:** 20 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q29j-3f7p-x46x

## What is CVE-2007-4427?

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

### Official description

Unspecified vulnerability in the login page redirection logic in the Cache' Server Page (CSP) implementation in InterSystems Cache' 2007.1.0.369.0 and 2007.1.1.420.0 allows remote authenticated users to modify data on a server, related to encoding of certain parameter values by this redirection logic, aka MAK2116.

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

It affects 1 product.


Products: Intersystems Cache Database.

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

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

## Is CVE-2007-4427 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-1333](https://insights.sbomify.com/CVE-2003-1333/): Other in n/a (critical 10.0)
- [CVE-2003-0497](https://insights.sbomify.com/CVE-2003-0497/): Privilege escalation in n/a (high 7.2)
- [CVE-2003-0498](https://insights.sbomify.com/CVE-2003-0498/): Code injection in n/a (high 7.2)
- [CVE-2007-0437](https://insights.sbomify.com/CVE-2007-0437/): Cross-site scripting in n/a (low 3.5)
- [CVE-2004-2684](https://insights.sbomify.com/CVE-2004-2684/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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