# CVE-2010-0744: Security feature bypass in n/a

> Man-in-the-middle attackers can spoof MSN servers by bypassing SSL hostname verification in aMSN when SSL is enabled.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/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:** 20 Apr 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p9f4-9pfr-g2fp

## What is CVE-2010-0744?

CVE-2010-0744 is a medium-severity vulnerability in n/a, published on 20 Apr 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

aMSN (aka Alvaro's Messenger) 0.98.3 and earlier, when SSL is used, does not verify that the server hostname matches a domain name in the subject's Common Name (CN) field or a Subject Alternative Name field of the X.509 certificate, which allows man-in-the-middle attackers to spoof an MSN server via an arbitrary certificate.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2010-0744?

It affects 1 product.


Products: Alvaro Alvaros Messenger.

## How do I fix CVE-2010-0744?

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

## Is CVE-2010-0744 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2195](https://insights.sbomify.com/CVE-2007-2195/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0744 and fix it if it is affected.

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

## Sources

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

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