Bug 1027754 (CVE-2013-5458) - CVE-2013-5458 IBM JDK: unspecified sandbox bypass (XML)
Summary: CVE-2013-5458 IBM JDK: unspecified sandbox bypass (XML)
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2013-5458
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1017632
TreeView+ depends on / blocked
 
Reported: 2013-11-07 11:29 UTC by Tomas Hoger
Modified: 2019-09-29 13:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-07 21:03:54 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1507 0 normal SHIPPED_LIVE Critical: java-1.7.0-ibm security update 2013-11-07 21:55:25 UTC

Description Tomas Hoger 2013-11-07 11:29:48 UTC 
An unspecified Java sandbox bypass issue in the XML component was fixed in IBM JDK 7 SR6.  This issue got the following CVSSv2 score upstream: 9.3/AV:N/AC:M/Au:N/C:C/I:C/A:C

https://www.ibm.com/developerworks/java/jdk/alerts/#IBM_Security_Update_November_2013
https://www.ibm.com/developerworks/java/jdk/aix/j732/Java7.fixes.html#SR6

Further info is available in this WebSphere Real Time security bulletin:

http://www-01.ibm.com/support/docview.wss?uid=swg21655202&myns=swgws&mynp=OCSSSTCZ&mync=R

  CVE-2013-5456, CVE-2013-5457 and CVE-2013-5458 allow code running under a
  security manager to escalate its privileges by modifying or removing the
  security manager.

Additional details may become available under this X-Force database article:

http://xforce.iss.net/xforce/xfdb/88257
Comment 1 errata-xmlrpc 2013-11-07 17:15:35 UTC 
This issue has been addressed in following products:

  Supplementary for Red Hat Enterprise Linux 5
  Supplementary for Red Hat Enterprise Linux 6

Via RHSA-2013:1507 https://rhn.redhat.com/errata/RHSA-2013-1507.html
Note You need to log in before you can comment on or make changes to this bug.