Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 514070 - (CVE-2009-1724) CVE-2009-1724 kdelibs: possible XSS vulnerability
CVE-2009-1724 kdelibs: possible XSS vulnerability
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
http://web.nvd.nist.gov/view/vuln/det...
impact=moderate,source=debian,reporte...
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-27 16:17 EDT by Vincent Danen
Modified: 2016-03-04 06:16 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-08-06 11:11:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Vincent Danen 2009-07-27 16:17:13 EDT
CVE-2009-1724 was originally given to a Safari Webkit issue:

Cross-site scripting (XSS) vulnerability in WebKit in Apple Safari before 4.0.2 allows remote attackers to inject arbitrary web script or HTML via vectors related to parent and top objects.

According to two Debian bug reports ([1], [2]) this may affect qt4 and webkit, which means it may also affect kdelibs.  I am unable to find any patches for qt4 or webkit as of yet.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538403 (qt4-x11)
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538402 (webkit)
Comment 5 Jan Lieskovsky 2009-08-06 10:32:09 EDT
Official statement from Red Hat Security Response Team regarding this issue:
----------------------------------------------------------------------------

Not vulnerable. This issue did not affect the versions of the kdelibs
package, as shipped with Red Hat Enterprise Linux 3, 4, or 5.

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