What is the severity of CVE-2005-3351?

CVE-2005-3351 is considered a moderate severity vulnerability that allows attackers to bypass spam detection in SpamAssassin 3.0.4.

How do I fix CVE-2005-3351?

To fix CVE-2005-3351, upgrade SpamAssassin to a newer version that addresses this vulnerability.

What are the effects of CVE-2005-3351?

CVE-2005-3351 can cause a bus error in Perl, potentially allowing spam emails to be processed without detection.

Which version of SpamAssassin is affected by CVE-2005-3351?

CVE-2005-3351 specifically affects SpamAssassin version 3.0.4.

How can I mitigate the risk associated with CVE-2005-3351?

To mitigate the risk of CVE-2005-3351, consider implementing additional email filtering mechanisms alongside an upgrade to a patched version of SpamAssassin.

Vulnerability/
CVE-2005-3351

medium

CWE

NVD-CWE-Other

20/11/2005

7/8/2024

CVE-2005-3351

First published: Sun Nov 20 2005(Updated: )

SpamAssassin 3.0.4 allows attackers to bypass spam detection via an e-mail with a large number of recipients ("To" addresses), which triggers a bus error in Perl.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
Apache SpamAssassin	=3.0.4

Remedy

http://lwn.net/Alerts/159300/

Remedy

http://www.gossamer-threads.com/lists/spamassassin/devel/62649

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2005-3351?
CVE-2005-3351 is considered a moderate severity vulnerability that allows attackers to bypass spam detection in SpamAssassin 3.0.4.
How do I fix CVE-2005-3351?
To fix CVE-2005-3351, upgrade SpamAssassin to a newer version that addresses this vulnerability.
What are the effects of CVE-2005-3351?
CVE-2005-3351 can cause a bus error in Perl, potentially allowing spam emails to be processed without detection.
Which version of SpamAssassin is affected by CVE-2005-3351?
CVE-2005-3351 specifically affects SpamAssassin version 3.0.4.
How can I mitigate the risk associated with CVE-2005-3351?
To mitigate the risk of CVE-2005-3351, consider implementing additional email filtering mechanisms alongside an upgrade to a patched version of SpamAssassin.

collector/nvd-historical
collector/nvd-index
agent/type
agent/softwarecombine
agent/remedy
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/references
agent/last-modified-date
agent/author
agent/description
agent/event
agent/tags
agent/first-publish-date
agent/source
vendor/apache
canonical/apache spamassassin
version/apache spamassassin/3.0.4

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2005-3351?
CVE-2005-3351 is considered a moderate severity vulnerability that allows attackers to bypass spam detection in SpamAssassin 3.0.4.
How do I fix CVE-2005-3351?
To fix CVE-2005-3351, upgrade SpamAssassin to a newer version that addresses this vulnerability.
What are the effects of CVE-2005-3351?
CVE-2005-3351 can cause a bus error in Perl, potentially allowing spam emails to be processed without detection.
Which version of SpamAssassin is affected by CVE-2005-3351?
CVE-2005-3351 specifically affects SpamAssassin version 3.0.4.
How can I mitigate the risk associated with CVE-2005-3351?
To mitigate the risk of CVE-2005-3351, consider implementing additional email filtering mechanisms alongside an upgrade to a patched version of SpamAssassin.