CVE-2006-2203 Security feature bypass in n/a
Medium 6.4
Published
Updated
Check this codebase for CVE-2006-2203 and fix it if it is affected.
What it is: CVE-2006-2203 is a medium-severity vulnerability in n/a, published on 5 May 2006. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2006-2203 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-2006-2203/ (Markdown: https://insights.sbomify.com/CVE-2006-2203/index.md)
Attackers can bypass attachment filters in Kerio MailServer, potentially allowing malicious files to reach recipients.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Over the internet
- Victim action needed
- Not stated
- Fix
- None listed
What is CVE-2006-2203?
CVE-2006-2203 is a medium-severity vulnerability in n/a, published on 5 May 2006. It can be exploited over the network.
Official description
Unspecified vulnerability in Kerio MailServer before 6.1.4 has unknown impact and remote attack vectors related to a "possible bypass of attachment filter."
Which versions are affected by CVE-2006-2203?
It affects 1 product.
Products include Kerio Kerio Mailserver.
How do I fix CVE-2006-2203?
No fix has been published for CVE-2006-2203 yet. Limit exposure of the affected software until one is available.
Is CVE-2006-2203 being exploited?
There is no known exploitation of CVE-2006-2203 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-j77x-c2h6-pqpg.