# CVE-2001-0788: Information disclosure in n/a

> Remote attackers can obtain the absolute path of the server directory by viewing the Location header in Internet Software Solutions Air Messenger LAN Server.

- **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:** 12 Oct 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-m7h7-j2x5-9v3x

## What is CVE-2001-0788?

CVE-2001-0788 is a medium-severity vulnerability in n/a, published on 12 Oct 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Internet Software Solutions Air Messenger LAN Server (AMLServer) 3.4.2 allows remote attackers to obtain an absolute path for the server directory by viewing the Location header.

## Which versions are affected by CVE-2001-0788?

It affects 1 product.


Products: Internet Software Solutions Air Messenger Lan Server.

## How do I fix CVE-2001-0788?

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

## Is CVE-2001-0788 being exploited?

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

Public exploit code:

- Internet Software Solutions Air Messenger LAN Server 3.4.2 - Full Path Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-0785](https://insights.sbomify.com/CVE-2001-0785/): Path traversal in n/a (medium 5.0)
- [CVE-2001-0786](https://insights.sbomify.com/CVE-2001-0786/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0788 and fix it if it is affected.

What it is: CVE-2001-0788 is a medium-severity vulnerability in n/a, published on 12 Oct 2001. 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-2001-0788 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-2001-0788/ (Markdown: https://insights.sbomify.com/CVE-2001-0788/index.md)
```

## Sources

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

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