Bug 2366287 (CVE-2025-3875)

Summary: CVE-2025-3875 thunderbird: Sender Spoofing via Malformed From Header in Thunderbird
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: erack, gotiwari, jhorak, mvyas, tpopela
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
The Mozilla Foundation's Security Advisory describes the following issue: Thunderbird parses addresses in a way that can allow sender spoofing in case the server allows an invalid From address to be used. For example, if the From header contains an (invalid) value "Spoofed Name spoofed@example.com legitimate@example.com", Thunderbird treats spoofed@example.com as the actual address.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2025-05-14 18:01:44 UTC
Thunderbird parses addresses in a way that can allow sender spoofing in case the server allows an invalid From address to be used. For example, if the From header contains an (invalid) value "Spoofed Name  ", Thunderbird treats spoofed as the actual address. This vulnerability affects Thunderbird < 128.10.1 and Thunderbird < 138.0.1.

Comment 1 errata-xmlrpc 2025-05-27 10:01:06 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2025:8196 https://access.redhat.com/errata/RHSA-2025:8196

Comment 2 errata-xmlrpc 2025-05-27 12:22:35 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:8203 https://access.redhat.com/errata/RHSA-2025:8203

Comment 3 errata-xmlrpc 2025-05-29 19:29:53 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Extended Update Support

Via RHSA-2025:8326 https://access.redhat.com/errata/RHSA-2025:8326

Comment 4 errata-xmlrpc 2025-05-29 21:28:24 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions

Via RHSA-2025:8324 https://access.redhat.com/errata/RHSA-2025:8324

Comment 5 errata-xmlrpc 2025-05-29 22:54:00 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Extended Update Support

Via RHSA-2025:8325 https://access.redhat.com/errata/RHSA-2025:8325

Comment 6 errata-xmlrpc 2025-06-02 17:29:01 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.2 Advanced Update Support

Via RHSA-2025:8391 https://access.redhat.com/errata/RHSA-2025:8391

Comment 7 errata-xmlrpc 2025-06-04 11:43:47 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support

Via RHSA-2025:8507 https://access.redhat.com/errata/RHSA-2025:8507

Comment 8 errata-xmlrpc 2025-06-05 10:54:51 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.6 Telecommunications Update Service

Via RHSA-2025:8594 https://access.redhat.com/errata/RHSA-2025:8594

Comment 9 errata-xmlrpc 2025-06-10 09:38:25 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2025:8756 https://access.redhat.com/errata/RHSA-2025:8756

Comment 10 errata-xmlrpc 2025-06-10 15:05:07 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.8 Telecommunications Update Service

Via RHSA-2025:8784 https://access.redhat.com/errata/RHSA-2025:8784