# CVE-2009-5131: Security feature bypass in n/a

> Remote attackers can bypass email blacklist restrictions by using unrecognized domain extensions, allowing unauthorized email delivery.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/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:** 26 Aug 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-mp2h-r29x-p8v7

## What is CVE-2009-5131?

CVE-2009-5131 is a medium-severity vulnerability in n/a, published on 26 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Receive Service in Websense Email Security before 7.1 does not recognize domain extensions in the blacklist, which allows remote attackers to bypass intended access restrictions and send e-mail messages via an SMTP session.

Weakness: CWE-264

## Which versions are affected by CVE-2009-5131?

It affects 1 product.


Products: Websense Websense Email Security.

## How do I fix CVE-2009-5131?

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

## Is CVE-2009-5131 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-5121](https://insights.sbomify.com/CVE-2009-5121/): Security feature bypass in n/a (medium 5.0)
- [CVE-2009-5122](https://insights.sbomify.com/CVE-2009-5122/): Information disclosure in n/a (medium 5.0)
- [CVE-2012-4605](https://insights.sbomify.com/CVE-2012-4605/): Weak cryptography in n/a (medium 5.0)
- [CVE-2009-5130](https://insights.sbomify.com/CVE-2009-5130/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-5131 and fix it if it is affected.

What it is: CVE-2009-5131 is a medium-severity vulnerability in n/a, published on 26 Aug 2012. 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-2009-5131 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-2009-5131/ (Markdown: https://insights.sbomify.com/CVE-2009-5131/index.md)
```

## Sources

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

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