# CVE-2004-1223: Information disclosure in n/a

> Remote attackers can obtain sensitive web server path information from F-Secure Policy Manager via unauthenticated HTTP requests.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6fq9-25jp-jqrj

## What is CVE-2004-1223?

CVE-2004-1223 is a medium-severity vulnerability in n/a, published on 15 Dec 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Management Agent in F-Secure Policy Manager 5.11.2810 allows remote attackers to gain sensitive information, such as the absolute path for the web server, via an HTTP request to fsmsh.dll without any parameters.

## Which versions are affected by CVE-2004-1223?

It affects 1 product.


Products: F-Secure Policy Manager.

## How do I fix CVE-2004-1223?

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

## Is CVE-2004-1223 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1223 exists.

Public exploit code:

- F-Secure Policy Manager 5.11 - 'FSMSH.dll' CGI Application Installation Full Path Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2011-1103](https://insights.sbomify.com/CVE-2011-1103/): Information disclosure in n/a (medium 5.0)
- [CVE-2007-2964](https://insights.sbomify.com/CVE-2007-2964/): Denial of service in n/a (medium 5.0)
- [CVE-2011-1102](https://insights.sbomify.com/CVE-2011-1102/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1223 and fix it if it is affected.

What it is: CVE-2004-1223 is a medium-severity vulnerability in n/a, published on 15 Dec 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1223 exists.

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-2004-1223/ (Markdown: https://insights.sbomify.com/CVE-2004-1223/index.md)
```

## Sources

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

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