# CVE-2007-4961: Information disclosure in n/a

> Attackers can sniff network traffic to capture cleartext MD5 password hashes, enabling unauthorized account access in Second Life.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 18 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xc4q-r4rw-49j6

## What is CVE-2007-4961?

CVE-2007-4961 is a high-severity vulnerability in n/a, published on 18 Sep 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The login_to_simulator method in Linden Lab Second Life, as used by the secondlife:// protocol handler and possibly other Second Life login mechanisms, sends an MD5 hash in cleartext in the passwd field, which allows remote attackers to login to an account by sniffing the network and then sending this hash to a Second Life authentication server.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 1 product.


Products: Lindenlab Second Life.

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

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

## Is CVE-2007-4961 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4961 is a high-severity vulnerability in n/a, published on 18 Sep 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-4961 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-4961/ (Markdown: https://insights.sbomify.com/CVE-2007-4961/index.md)
```

## Sources

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

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