# CVE-2008-7255: Information disclosure in n/a

> Attackers with physical access can hijack sessions by exploiting saved passwords on unattended workstations using aMSN.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2r6h-23v5-cm2p

## What is CVE-2008-7255?

CVE-2008-7255 is a medium-severity vulnerability in n/a, published on 20 Apr 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

login_screen.tcl in aMSN (aka Alvaro's Messenger) before 0.97.1 saves a password after logout, which allows physically proximate attackers to hijack a session by visiting an unattended workstation.

Weakness: CWE-255

## Which versions are affected by CVE-2008-7255?

It affects 1 product.


Products: Amsn Amsn.

## How do I fix CVE-2008-7255?

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

## Is CVE-2008-7255 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0138](https://insights.sbomify.com/CVE-2006-0138/): Denial of service in n/a (medium 5.0)
- [CVE-2004-2454](https://insights.sbomify.com/CVE-2004-2454/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-7255 and fix it if it is affected.

What it is: CVE-2008-7255 is a medium-severity vulnerability in n/a, published on 20 Apr 2010. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-7255 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-2008-7255/ (Markdown: https://insights.sbomify.com/CVE-2008-7255/index.md)
```

## Sources

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

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