14 results (0.002 seconds)

CVSS: 5.3EPSS: 0%CPEs: 8EXPL: 6

Postfix through 3.8.5 allows SMTP smuggling unless configured with smtpd_data_restrictions=reject_unauth_pipelining and smtpd_discard_ehlo_keywords=chunking (or certain other options that exist in recent versions). Remote attackers can use a published exploitation technique to inject e-mail messages with a spoofed MAIL FROM address, allowing bypass of an SPF protection mechanism. This occurs because Postfix supports <LF>.<CR><LF> but some other popular e-mail servers do not. To prevent attack variants (by always disallowing <LF> without <CR>), a different solution is required, such as the smtpd_forbid_bare_newline=yes option with a Postfix minimum version of 3.5.23, 3.6.13, 3.7.9, 3.8.4, or 3.9. • https://github.com/duy-31/CVE-2023-51764 https://github.com/eeenvik1/CVE-2023-51764 https://github.com/Double-q1015/CVE-2023-51764 https://github.com/d4op/CVE-2023-51764-POC http://www.openwall.com/lists/oss-security/2023/12/24/1 http://www.openwall.com/lists/oss-security/2023/12/25/1 http://www.openwall.com/lists/oss-security/2024/05/09/3 https://access.redhat.com/security/cve/CVE-2023-51764 https://bugzilla.redhat.com/show_bug.cgi?id=2255563 http • CWE-345: Insufficient Verification of Data Authenticity •

CVSS: 5.3EPSS: 0%CPEs: 1EXPL: 1

A certain Postfix 2.10.1-7 package could allow an attacker to send an email from an arbitrary-looking sender via a homoglyph attack, as demonstrated by the similarity of \xce\xbf to the 'o' character. This is potentially relevant when the /etc/postfix/sender_login feature is used, because a spoofed outbound message that uses a configured sender address is blocked with a "Sender address rejected: not logged in" error message, but a spoofed outbound message that uses a homoglyph of a configured sender address is not blocked. NOTE: some third parties argue that any missed blocking of spoofed outbound messages - except for exact matches to a sender address in the /etc/postfix/sender_login file - is outside the design goals of Postfix and thus cannot be considered a Postfix vulnerability ** EN DISPUTA ** Un determinado paquete Postfix versión 2.10.1-7, podría permitir a un atacante enviar un correo electrónico desde un remitente de aspecto arbitrario por medio de un ataque de Homoglifo, como es demostrado por la similitud de \xce\xbf con el carácter "o". Esto es potencialmente relevante cuando es usada la funcionalidad /etc/postfix/sender_login, porque un mensaje saliente falso que usa una dirección de remitente configurada es bloqueado con un mensaje de error "Sender address rejected: not logged in", pero un mensaje saliente falso que usa un homoglifo de una dirección de remitente configurada no es bloqueado. NOTA: Algunos terceros sostienen que cualquier bloqueo omitido de mensajes salientes falsos - excepto por coincidencias exactas con una dirección del remitente en el archivo de /etc/postfix/sender_login - está fuera de los objetivos de diseño de Postfix y, por lo tanto, no puede ser considerada una vulnerabilidad de Postfix. • https://www.openwall.com/lists/oss-security/2020/04/23/12 https://www.openwall.com/lists/oss-security/2020/04/23/3 •

CVSS: 6.9EPSS: 0%CPEs: 1EXPL: 0

In postfix-mta-sts-resolver before 0.5.1, All users can receive incorrect response from daemon under rare conditions, rendering downgrade of effective STS policy. En postfix-mta-sts-resolver versiones anteriores a 0.5.1, todos los usuarios pueden recibir una respuesta incorrecta del demonio bajo condiciones extrañas, renderizando una degradación de la política STS efectiva. • https://gist.github.com/Snawoot/b9da85d6b26dea5460673b29df1adc6b https://github.com/Snawoot/postfix-mta-sts-resolver/security/advisories/GHSA-h92m-42h4-82f6 • CWE-757: Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade') •

CVSS: 7.8EPSS: 0%CPEs: 4EXPL: 1

Postfix before 2.11.10, 3.0.x before 3.0.10, 3.1.x before 3.1.6, and 3.2.x before 3.2.2 might allow local users to gain privileges by leveraging undocumented functionality in Berkeley DB 2.x and later, related to reading settings from DB_CONFIG in the current directory. Postfix, en versiones anteriores a la 2.11.10, versiones 3.0.x anteriores a la 3.0.10, versiones 3.1.x anteriores a la 3.1.6 y versiones 3.2.x anteriores a la 3.2.2, podría permitir que usuarios locales obtengan privilegios aprovechando una funcionalidad no documentada en Berkeley DB, en versiones 2.x y posteriores. Esto está relacionado con la lectura de opciones de DB_CONFIG en el directorio actual. • http://seclists.org/oss-sec/2017/q3/285 http://www.postfix.org/announcements/postfix-3.2.2.html https://access.redhat.com/errata/RHSA-2019:0366 https://www.oracle.com/security-alerts/cpujul2020.html https://access.redhat.com/security/cve/CVE-2017-10140 https://bugzilla.redhat.com/show_bug.cgi?id=1464032 •

CVSS: 6.5EPSS: 0%CPEs: 8EXPL: 1

SQL injection vulnerability in the gen_show_status function in functions.inc.php in Postfix Admin (aka postfixadmin) before 2.3.7 allows remote authenticated users to execute arbitrary SQL commands via a new alias. Vulnerabilidad de inyección SQL en la función gen_show_status en functions.inc.php en Postfix Admin (también conocido como postfixadmin) anterior a 2.3.7 permite a usuarios remotos autenticados ejecutar comandos SQL arbitrarios a través de un alias nuevo. • http://lists.opensuse.org/opensuse-updates/2014-05/msg00075.html http://sourceforge.net/p/postfixadmin/code/1650 http://www.debian.org/security/2014/dsa-2889 http://www.openwall.com/lists/oss-security/2014/03/26/11 http://www.openwall.com/lists/oss-security/2014/03/26/6 http://www.securityfocus.com/bid/66455 • CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') •