Filtered by vendor Roaring Penguin Subscriptions

Search

Switch to Advanced Search (Beta)
Total 6 CVE
CVE Vendors Products Updated CVSS v3.1
CVE-2015-5957 2 Opensuse, Roaring Penguin 2 Opensuse, Remind 2025-04-12 N/A
Buffer overflow in the DumpSysVar function in var.c in Remind before 3.1.15 allows attackers to have unspecified impact via a long name.
CVE-2007-0884 1 Roaring Penguin 1 Mimedefang 2025-04-09 N/A
Buffer overflow in Roaring Penguin MIMEDefang 2.59 and 2.60 allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via unspecified vectors.
CVE-2001-0026 1 Roaring Penguin 1 Pppoe 2025-04-03 N/A
rp-pppoe PPPoE client allows remote attackers to cause a denial of service via the Clamp MSS option and a TCP packet with a zero-length TCP option.
CVE-2004-1098 3 Mandrakesoft, Roaring Penguin, Suse 4 Mandrake Linux, Mandrake Linux Corporate Server, Mimedefang and 1 more 2025-04-03 N/A
MIMEDefang in MIME-tools 5.414 allows remote attackers to bypass virus scanning capabilities via an e-mail attachment with a virus that contains an empty boundary string in the Content-Type header.
CVE-2002-1121 4 Gfi, Network Associates, Roaring Penguin and 1 more 5 Mailsecurity, Webshield Smtp, Canit and 2 more 2025-04-03 N/A
SMTP content filter engines, including (1) GFI MailSecurity for Exchange/SMTP before 7.2, (2) InterScan VirusWall before 3.52 build 1494, (3) the default configuration of MIMEDefang before 2.21, and possibly other products, do not detect fragmented emails as defined in RFC2046 ("Message Fragmentation and Reassembly") and supported in such products as Outlook Express, which allows remote attackers to bypass content filtering, including virus checking, via fragmented emails of the message/partial content type.
CVE-2004-0564 2 Debian, Roaring Penguin 2 Debian Linux, Pppoe 2025-04-03 N/A
Roaring Penguin pppoe (rp-ppoe), if installed or configured to run setuid root contrary to its design, allows local users to overwrite arbitrary files. NOTE: the developer has publicly disputed the claim that this is a vulnerability because pppoe "is NOT designed to run setuid-root." Therefore this identifier applies *only* to those configurations and installations under which pppoe is run setuid root despite the developer's warnings.