Bug 2375544 - CVE-2025-49179 tigervnc: Integer overflow in X Record extension [fedora-41]
Summary: CVE-2025-49179 tigervnc: Integer overflow in X Record extension [fedora-41]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: tigervnc
Version: 41
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Jan Grulich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["3d4960ff-b6f6-4194-ad33-e...
Depends On:
Blocks: CVE-2025-49179
TreeView+ depends on / blocked
 
Reported: 2025-06-30 08:53 UTC by Dhananjay Arunesh
Modified: 2025-12-03 01:06 UTC (History)
1 user (show)

Fixed In Version: tigervnc-1.15.0-10.fc43 tigervnc-1.15.0-10.fc42
Clone Of:
Environment:
Last Closed: 2025-12-03 00:52:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dhananjay Arunesh 2025-06-30 08:53:30 UTC
More information about this security flaw is available in the following bug:

https://bugzilla.redhat.com/show_bug.cgi?id=2369978

Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Comment 1 Fedora Update System 2025-11-24 07:56:55 UTC
FEDORA-2025-f59b250c31 (tigervnc-1.15.0-10.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-f59b250c31

Comment 2 Fedora Update System 2025-11-24 07:57:18 UTC
FEDORA-2025-e0c935675d (tigervnc-1.15.0-10.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-e0c935675d

Comment 3 Fedora Update System 2025-11-25 01:59:07 UTC
FEDORA-2025-e0c935675d has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-e0c935675d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-e0c935675d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2025-11-25 02:21:35 UTC
FEDORA-2025-f59b250c31 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-f59b250c31`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-f59b250c31

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Adam Williamson 2025-12-02 03:11:09 UTC
This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '41'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 41 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Fedora Update System 2025-12-03 00:52:40 UTC
FEDORA-2025-e0c935675d (tigervnc-1.15.0-10.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2025-12-03 01:06:01 UTC
FEDORA-2025-f59b250c31 (tigervnc-1.15.0-10.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.