|
Vulnerability Report: Qt 4.x
|
This vulnerability report for Qt 4.x contains a complete overview of all Secunia advisories affecting it. You can use this vulnerability report to ensure that you are aware of all vulnerabilities, both patched and unpatched, affecting this product allowing you to take the necessary precautions.
If you have information about a new or an existing vulnerability in Qt 4.x then you are more than welcome to contact us.
|
|
|
|
|
Vendor, Links, and Unpatched Vulnerabilities
| Vendor |
Trolltech
|
|
|
Product Link
|
View Here (Link to external site)
|
|
|
Affected By
|
7 Secunia advisories
16 Vulnerabilities
|
|
|
Monitor Product
|
Receive alerts for this product
|
|
|
Unpatched
|
14% (1 of 7 Secunia advisories)
|
|
Most Critical Unpatched
The most severe unpatched Secunia advisory affecting Qt 4.x, with all vendor patches applied, is rated Highly critical  .
|
|
|
|
|
|
7 Secunia Advisories in 2003-2009
|
Secunia has issued a total of 7 Secunia advisories in 2003-2009 for Qt 4.x. Currently, 14% (1 out of 7) are marked as unpatched with the most severe being rated Highly critical
More information about the specific Secunia advisories affecting Qt 4.x can be found below. Each Secunia advisory is enclosed by a box highlighted with a color representing its current patch status. You can read the complete Secunia advisories for thorough descriptions of the issues covered and for solution suggestions by clicking either the Secunia advisory title or the "Read More" links available for each Secunia advisory.
|
|
|
|
|
|
Release Date:
2009-11-16 |
Secunia Advisory ID:
SA37396 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
Security Bypass
Exposure of sensitive information
System access
|
Where:
From remote |
|
Short Description:
Some vulnerabilities have been reported in Qt, which can be exploited by malicious people to disclose sensitive information, bypass certain security restrictions, or compromise a user's system. [Read More]
|
|
|
|
|
|
Release Date:
2009-11-16 |
Secunia Advisory ID:
SA37393 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
Security Bypass
System access
|
Where:
From remote |
|
Short Description:
Some vulnerabilities have been reported in Qt, which can be exploited by malicious people to bypass certain security restrictions, disclose sensitive information, or compromise an application using the library. [Read More]
|
|
|
|
|
|
Release Date:
2009-09-01 |
Secunia Advisory ID:
SA36536 |
Solution Status:
Vendor Workaround |
|
Criticality:
 |
Impact:
Spoofing
|
Where:
From remote |
|
Short Description:
A vulnerability has been reported in Qt, which can be exploited by malicious people to conduct spoofing attacks. [Read More]
|
|
|
|
|
|
Release Date:
2008-01-03 |
Secunia Advisory ID:
SA28228 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
Security Bypass
Spoofing
|
Where:
From remote |
|
Short Description:
A vulnerability has been reported in Qt, which can be exploited by malicious people to bypass certain security restrictions. [Read More]
|
|
|
|
|
|
Release Date:
2007-09-14 |
Secunia Advisory ID:
SA26811 |
Solution Status:
Vendor Patch |
|
Criticality:
 |
Impact:
DoS
System access
|
Where:
From remote |
|
Short Description:
A vulnerability has been reported in Qt, which can potentially be exploited by malicious people to cause a DoS (Denial of Service) or to compromise an application using the library. [Read More]
|
|
|
|
|
|
Release Date:
2007-04-03 |
Secunia Advisory ID:
SA24727 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
Cross Site Scripting
|
Where:
From remote |
|
Short Description:
Andreas Nolden has reported a vulnerability in Qt, which potentially can be exploited to conduct cross-site scripting attacks in applications using the Qt libraries. [Read More]
|
|
|
|
|
|
Release Date:
2006-10-19 |
Secunia Advisory ID:
SA22380 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
DoS
System access
|
Where:
From remote |
|
Short Description:
A vulnerability has been reported in Qt, which can be exploited by malicious people to cause a DoS (Denial of Service) and potentially compromise an application using the library. [Read More]
|
|
|
