Bug 2343762 (CVE-2025-0510) - CVE-2025-0510 thunderbird: Address of e-mail sender can be spoofed by malicious email
Summary: CVE-2025-0510 thunderbird: Address of e-mail sender can be spoofed by malicio...
Keywords:
Status: NEW
Alias: CVE-2025-0510
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-04 15:02 UTC by OSIDB Bzimport
Modified: 2025-09-01 08:28 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:1184 0 None None None 2025-02-10 01:23:25 UTC
Red Hat Product Errata RHSA-2025:1292 0 None None None 2025-02-11 11:24:50 UTC
Red Hat Product Errata RHSA-2025:1317 0 None None None 2025-02-11 16:36:55 UTC
Red Hat Product Errata RHSA-2025:1318 0 None None None 2025-02-11 16:38:41 UTC
Red Hat Product Errata RHSA-2025:1319 0 None None None 2025-02-11 15:51:57 UTC
Red Hat Product Errata RHSA-2025:1339 0 None None None 2025-02-12 04:05:35 UTC
Red Hat Product Errata RHSA-2025:1340 0 None None None 2025-02-12 04:12:12 UTC
Red Hat Product Errata RHSA-2025:1341 0 None None None 2025-02-12 04:19:09 UTC
Red Hat Product Errata RHSA-2025:1348 0 None None None 2025-02-12 09:35:19 UTC

Description OSIDB Bzimport 2025-02-04 15:02:09 UTC 
Thunderbird displayed an incorrect sender address if the From field of an email used the invalid group name syntax that is described in CVE-2024-49040. This vulnerability affects Thunderbird < 128.7 and Thunderbird < 135.
Comment 1 errata-xmlrpc 2025-02-10 01:23:24 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:1184 https://access.redhat.com/errata/RHSA-2025:1184
Comment 2 errata-xmlrpc 2025-02-11 11:24:48 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2025:1292 https://access.redhat.com/errata/RHSA-2025:1292
Comment 3 errata-xmlrpc 2025-02-11 15:51:55 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions

Via RHSA-2025:1319 https://access.redhat.com/errata/RHSA-2025:1319
Comment 4 errata-xmlrpc 2025-02-11 16:36:53 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Extended Update Support

Via RHSA-2025:1317 https://access.redhat.com/errata/RHSA-2025:1317
Comment 5 errata-xmlrpc 2025-02-11 16:38:40 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Extended Update Support

Via RHSA-2025:1318 https://access.redhat.com/errata/RHSA-2025:1318
Comment 6 errata-xmlrpc 2025-02-12 04:05:34 UTC 
This issue has been addressed in the following products:

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

Via RHSA-2025:1339 https://access.redhat.com/errata/RHSA-2025:1339
Comment 7 errata-xmlrpc 2025-02-12 04:12:11 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.8 Extended Update Support

Via RHSA-2025:1340 https://access.redhat.com/errata/RHSA-2025:1340
Comment 8 errata-xmlrpc 2025-02-12 04:19:08 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:1341 https://access.redhat.com/errata/RHSA-2025:1341
Comment 9 errata-xmlrpc 2025-02-12 09:35:18 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.2 Advanced Update Support

Via RHSA-2025:1348 https://access.redhat.com/errata/RHSA-2025:1348
Note You need to log in before you can comment on or make changes to this bug.