# CVE-2007-3464: Cross-site request forgery in n/a

> Attackers can change the admin password via CSRF without the old password, leading to privilege escalation and account takeover on Check Point Safe@Office devices.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pwm5-359r-f8qp

## What is CVE-2007-3464?

CVE-2007-3464 is a high-severity vulnerability in n/a, published on 27 Jun 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Check Point SofaWare Safe@Office, with firmware before Embedded NGX 7.0.45 GA, does not require entry of the old password when changing the admin password, which might allow attackers to gain privileges by conducting a CSRF attack, making a password change on an unattended workstation, or other vectors.

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

It affects 1 product.


Products: Sofaware Safe at Office 500 Utm.

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

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

## Is CVE-2007-3464 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3465](https://insights.sbomify.com/CVE-2007-3465/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2007-3462](https://insights.sbomify.com/CVE-2007-3462/): Cross-site request forgery in n/a (medium 6.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3464 is a high-severity vulnerability in n/a, published on 27 Jun 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-3464 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-3464/ (Markdown: https://insights.sbomify.com/CVE-2007-3464/index.md)
```

## Sources

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

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