10
CVSSv2

CVE-2010-3559

Published: 19/10/2010 Updated: 30/10/2018
CVSS v2 Base Score: 10 | Impact Score: 10 | Exploitability Score: 10
VMScore: 890
Vector: AV:N/AC:L/Au:N/C:C/I:C/A:C

Vulnerability Summary

Unspecified vulnerability in the Sound component in Oracle Java SE and Java for Business 6 Update 21, 5.0 Update 25, 1.4.2_27, and 1.3.1_28 allows remote malicious users to affect confidentiality, integrity, and availability via unknown vectors. NOTE: the previous information was obtained from the October 2010 CPU. Oracle has not commented on claims from a reliable researcher that this involves an incorrect sign extension in the HeadspaceSoundbank.nGetName function, which allows malicious users to execute arbitrary code via a crafted BANK record that leads to a buffer overflow.

Vulnerable Product Search on Vulmon Subscribe to Product

sun jre 1.6.0

sun jre

sun jdk 1.6.0

sun jdk

sun jdk 1.5.0

sun sdk 1.4.2

sun sdk 1.4.2_15

sun sdk 1.4.2_16

sun sdk 1.4.2_6

sun sdk 1.4.2_7

sun sdk 1.4.2_24

sun sdk 1.4.2_25

sun sdk 1.4.2_26

sun sdk 1.4.2_13

sun sdk 1.4.2_14

sun sdk 1.4.2_4

sun sdk 1.4.2_5

sun sdk 1.4.2_22

sun sdk 1.4.2_23

sun sdk 1.4.2_11

sun sdk 1.4.2_12

sun sdk 1.4.2_19

sun sdk 1.4.2_3

sun sdk 1.4.2_20

sun sdk 1.4.2_21

sun sdk 1.4.2_02

sun sdk 1.4.2_1

sun sdk 1.4.2_10

sun sdk 1.4.2_17

sun sdk 1.4.2_18

sun sdk 1.4.2_8

sun sdk 1.4.2_9

sun sdk

sun jre 1.5.0

sun jre 1.4.2_2

sun jre 1.4.2_3

sun jre 1.4.2_10

sun jre 1.4.2_18

sun jre 1.4.2_19

sun jre 1.4.2_26

sun jre 1.4.2

sun jre 1.4.2_1

sun jre 1.4.2_8

sun jre 1.4.2_9

sun jre 1.4.2_15

sun jre 1.4.2_16

sun jre 1.4.2_17

sun jre 1.4.2_24

sun jre 1.4.2_25

sun jre 1.4.2_6

sun jre 1.4.2_7

sun jre 1.4.2_13

sun jre 1.4.2_14

sun jre 1.4.2_22

sun jre 1.4.2_23

sun jre 1.4.2_4

sun jre 1.4.2_5

sun jre 1.4.2_11

sun jre 1.4.2_12

sun jre 1.4.2_20

sun jre 1.4.2_21

sun jdk 1.3.0_05

sun jdk 1.3.1

sun jdk 1.3.1_07

sun jdk 1.3.1_08

sun jdk 1.3.1_14

sun jdk 1.3.1_16

sun jdk 1.3.1_23

sun jdk 1.3.1_24

sun jdk 1.3.0_03

sun jdk 1.3.0_04

sun jdk 1.3.1_05

sun jdk 1.3.1_06

sun jdk 1.3.1_13

sun jdk 1.3.1_15

sun jdk 1.3.1_21

sun jdk 1.3.1_22

sun jdk 1.3.0_01

sun jdk 1.3.0_02

sun jdk 1.3.1_02

sun jdk 1.3.1_03

sun jdk 1.3.1_04

sun jdk 1.3.1_11

sun jdk 1.3.1_12

sun jdk 1.3.1_19

sun jdk 1.3.1_20

sun jdk 1.3.0

sun jdk 1.3.1_01

sun jdk 1.3.1_01a

sun jdk 1.3.1_09

sun jdk 1.3.1_10

sun jdk 1.3.1_17

sun jdk 1.3.1_18

sun jdk 1.3.1_25

sun jdk 1.3.1_26

sun jdk 1.3.1_27

sun jre 1.3.0

sun jre 1.3.1_04

sun jre 1.3.1_05

sun jre 1.3.1_12

sun jre 1.3.1_13

sun jre 1.3.1_14

sun jre 1.3.1_20

sun jre 1.3.1

sun jre 1.3.1_03

sun jre 1.3.1_10

sun jre 1.3.1_11

sun jre 1.3.1_19

sun jre 1.3.1_2

sun jre 1.3.1_26

sun jre 1.3.1_27

sun jre 1.3.1_21

sun jre 1.3.1_08

sun jre 1.3.1_09

sun jre 1.3.1_17

sun jre 1.3.1_18

sun jre 1.3.1_24

sun jre 1.3.1_25

sun jre 1.3.1_06

sun jre 1.3.1_07

sun jre 1.3.1_15

sun jre 1.3.1_16

sun jre 1.3.1_22

sun jre 1.3.1_23

sun sdk 1.3.0_04

sun sdk 1.3.0_05

sun sdk 1.3.1_06

sun sdk 1.3.1_07

sun sdk 1.3.1_14

sun sdk 1.3.1_15

sun sdk 1.3.1_22

sun sdk 1.3.1_23

sun sdk 1.3.1_24

sun sdk 1.3.1

sun sdk 1.3.1_01

sun sdk 1.3.1_01a

sun sdk 1.3.1_08

sun sdk 1.3.1_09

sun sdk 1.3.1_16

sun sdk 1.3.1_17

sun sdk 1.3.1_25

sun sdk 1.3.1_26

sun sdk 1.3.0_02

sun sdk 1.3.0_03

sun sdk 1.3.1_04

sun sdk 1.3.1_05

sun sdk 1.3.1_12

sun sdk 1.3.1_13

sun sdk 1.3.1_20

sun sdk 1.3.1_21

sun sdk 1.3.0

sun sdk 1.3.0_01

sun sdk 1.3.1_02

sun sdk 1.3.1_03

sun sdk 1.3.1_10

sun sdk 1.3.1_11

sun sdk 1.3.1_18

sun sdk 1.3.1_19

sun sdk 1.3.1_27

Vendor Advisories

Synopsis Critical: java-160-sun security update Type/Severity Security Advisory: Critical Topic Updated java-160-sun packages that fix several security issues are nowavailable for Red Hat Enterprise Linux 4 Extras and 5 SupplementaryThe Red Hat Security Response Team has rated this update as having cri ...
MIT Kerberos contains a vulnerability that could allow an authenticated, remote attacker to cause a denial of service (DoS) condition The vulnerability is in the GSS-API acceptor component due to lack of pointer validation  An authenticated, remote attacker could exploit the vulnerability by making a crafted request to the affected componen ...