Vulnerability Database

326,895

Total vulnerabilities in the database

Vulnerabilities for products matching "jre"

Found 3 matching products. Filters apply to all results.

You can search for specific versions with /product/jre/1.2.3

oracle / jre

790 vulnerabilities found
Title Severity Exploit Date Affected Version
CVE-2013-2436
High April 17, 2013 4/17/13
<= 1.7.0
== 1.7.0
== 1.7.0-update1
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update13
== 1.7.0-update15
== 1.7.0-update2
== 1.7.0-update3
== 1.7.0-update4
== 1.7.0-update5
== 1.7.0-update6
== 1.7.0-update7
== 1.7.0-update9
CVE-2013-2438
Medium April 17, 2013 4/17/13
<= 1.7.0
== 1.7.0
== 1.7.0-update1
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update13
== 1.7.0-update15
== 1.7.0-update2
== 1.7.0-update3
== 1.7.0-update4
== 1.7.0-update5
== 1.7.0-update6
== 1.7.0-update7
== 1.7.0-update9
CVE-2013-2439
Medium April 17, 2013 4/17/13
== 1.7.0-update9
== 1.7.0-update15
== 1.7.0-update6
<= 1.7.0
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update41
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update40
<= 1.5.0
== 1.5.0-update38
CVE-2013-2440
High April 17, 2013 4/17/13
== 1.7.0-update9
== 1.7.0-update15
== 1.7.0-update6
<= 1.7.0
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update41
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
CVE-2013-1537
High April 17, 2013 4/17/13
== 1.7.0-update9
== 1.7.0-update15
== 1.7.0-update6
<= 1.7.0
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update41
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update40
<= 1.5.0
== 1.5.0-update38
CVE-2013-1540
Low April 17, 2013 4/17/13
== 1.7.0-update9
== 1.7.0-update15
== 1.7.0-update6
<= 1.7.0
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update41
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
CVE-2013-1557
High April 17, 2013 4/17/13
== 1.7.0-update9
== 1.7.0-update15
== 1.7.0-update6
<= 1.7.0
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update41
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update40
<= 1.5.0
== 1.5.0-update38
CVE-2013-1558
High April 17, 2013 4/17/13
== 1.7.0-update9
== 1.7.0-update15
== 1.7.0-update6
<= 1.7.0
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update41
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
CVE-2013-1561
Medium April 17, 2013 4/17/13
<= 1.7.0
== 1.7.0
== 1.7.0-update1
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update13
== 1.7.0-update15
== 1.7.0-update2
== 1.7.0-update3
== 1.7.0-update4
== 1.7.0-update5
== 1.7.0-update6
== 1.7.0-update7
== 1.7.0-update9
CVE-2013-1563
High April 17, 2013 4/17/13
== 1.7.0-update9
== 1.7.0-update15
== 1.7.0-update6
<= 1.7.0
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update41
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
CVE-2013-1564
Medium April 17, 2013 4/17/13
<= 1.7.0
== 1.7.0
== 1.7.0-update1
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update13
== 1.7.0-update15
== 1.7.0-update2
== 1.7.0-update3
== 1.7.0-update4
== 1.7.0-update5
== 1.7.0-update6
== 1.7.0-update7
== 1.7.0-update9
CVE-2013-1569
High April 17, 2013 4/17/13
== 1.7.0-update9
== 1.7.0-update15
== 1.7.0-update6
<= 1.7.0
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update41
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update40
<= 1.5.0
== 1.5.0-update38
CVE-2013-2383
High April 17, 2013 4/17/13
== 1.7.0-update9
== 1.7.0-update15
== 1.7.0-update6
<= 1.7.0
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update41
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update40
<= 1.5.0
== 1.5.0-update38
CVE-2013-2384
High April 17, 2013 4/17/13
== 1.7.0-update9
== 1.7.0-update15
== 1.7.0-update6
<= 1.7.0
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update41
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update40
<= 1.5.0
== 1.5.0-update38
CVE-2013-2394
High April 17, 2013 4/17/13
== 1.7.0-update9
== 1.7.0-update15
== 1.7.0-update6
<= 1.7.0
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update41
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update40
<= 1.5.0
== 1.5.0-update38
CVE-2013-2414
High April 17, 2013 4/17/13
<= 1.7.0
== 1.7.0
== 1.7.0-update1
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update13
== 1.7.0-update15
== 1.7.0-update2
== 1.7.0-update3
== 1.7.0-update4
== 1.7.0-update5
== 1.7.0-update6
== 1.7.0-update7
== 1.7.0-update9
CVE-2013-2415
Low April 17, 2013 4/17/13
<= 1.7.0
== 1.7.0
== 1.7.0-update1
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update13
== 1.7.0-update15
== 1.7.0-update2
== 1.7.0-update3
== 1.7.0-update4
== 1.7.0-update5
== 1.7.0-update6
== 1.7.0-update7
== 1.7.0-update9
CVE-2013-2416
Low April 17, 2013 4/17/13
<= 1.7.0
== 1.7.0
== 1.7.0-update1
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update13
== 1.7.0-update15
== 1.7.0-update2
== 1.7.0-update3
== 1.7.0-update4
== 1.7.0-update5
== 1.7.0-update6
== 1.7.0-update7
== 1.7.0-update9
CVE-2013-2417
Medium April 17, 2013 4/17/13
== 1.7.0-update9
== 1.7.0-update15
== 1.7.0-update6
<= 1.7.0
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update41
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update40
<= 1.5.0
== 1.5.0-update38
CVE-2013-2418
Low April 17, 2013 4/17/13
== 1.7.0-update9
== 1.7.0-update15
== 1.7.0-update6
<= 1.7.0
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update41
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
CVE-2013-2419
Medium April 17, 2013 4/17/13
== 1.7.0-update9
== 1.7.0-update15
== 1.7.0-update6
<= 1.7.0
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update41
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update40
<= 1.5.0
== 1.5.0-update38
CVE-2013-1518
High April 17, 2013 4/17/13
== 1.7.0-update9
== 1.7.0-update15
== 1.7.0-update6
<= 1.7.0
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update41
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update40
<= 1.5.0
== 1.5.0-update38
CVE-2013-0401
High March 8, 2013 3/8/13
== 1.7.0-update17
CVE-2013-0402
High March 8, 2013 3/8/13
== 1.7.0-update17
CVE-2013-1488
High March 8, 2013 3/8/13
== 1.7.0-update17
CVE-2013-1491
High March 8, 2013 3/8/13
== 1.7.0-update17
CVE-2013-1493
High March 5, 2013 3/5/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
<= 1.7.0
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
<= 1.5.0
== 1.5.0-update36
== 1.5.0-update38
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
CVE-2013-0809
High March 5, 2013 3/5/13
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
<= 1.6.0
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
<= 1.5.0
== 1.5.0-update36
== 1.5.0-update38
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
<= 1.7.0
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
CVE-2013-1484
High February 20, 2013 2/20/13
== 1.7.0
== 1.7.0-update1
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update3
== 1.7.0-update4
== 1.7.0-update5
== 1.7.0-update6
== 1.7.0-update7
== 1.7.0-update9
CVE-2013-1485
Medium February 20, 2013 2/20/13
== 1.7.0
== 1.7.0-update1
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update3
== 1.7.0-update4
== 1.7.0-update5
== 1.7.0-update6
== 1.7.0-update7
== 1.7.0-update9
CVE-2013-1486
High February 20, 2013 2/20/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update39
== 1.5.0-update38
CVE-2013-1487
High February 20, 2013 2/20/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update13
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update39
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
CVE-2013-0437
High February 2, 2013 2/2/13
== 1.7.0
== 1.7.0-update1
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update3
== 1.7.0-update4
== 1.7.0-update5
== 1.7.0-update6
== 1.7.0-update7
== 1.7.0-update9
CVE-2013-0438
Low February 2, 2013 2/2/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
CVE-2013-0440
Medium February 2, 2013 2/2/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update38
<= 1.4.2_40
== 1.4.2_38
CVE-2013-0441
High February 2, 2013 2/2/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update38
<= 1.4.2_40
== 1.4.2_38
CVE-2013-0442
High February 2, 2013 2/2/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update38
<= 1.4.2_40
== 1.4.2_38
CVE-2013-0443
Low February 2, 2013 2/2/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update38
<= 1.4.2_40
== 1.4.2_38
CVE-2013-0444
High February 2, 2013 2/2/13
== 1.7.0
== 1.7.0-update1
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update3
== 1.7.0-update4
== 1.7.0-update5
== 1.7.0-update6
== 1.7.0-update7
== 1.7.0-update9
CVE-2013-0445
High February 2, 2013 2/2/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update38
CVE-2013-0446
High February 2, 2013 2/2/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
CVE-2013-0448
Medium February 2, 2013 2/2/13
== 1.7.0
== 1.7.0-update1
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update3
== 1.7.0-update4
== 1.7.0-update5
== 1.7.0-update6
== 1.7.0-update7
== 1.7.0-update9
CVE-2013-0449
Medium February 2, 2013 2/2/13
== 1.7.0
== 1.7.0-update1
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update3
== 1.7.0-update4
== 1.7.0-update5
== 1.7.0-update6
== 1.7.0-update7
== 1.7.0-update9
CVE-2013-0450
High February 2, 2013 2/2/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update38
CVE-2013-1473
Medium February 2, 2013 2/2/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
CVE-2013-1475
High February 2, 2013 2/2/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update38
<= 1.4.2_40
== 1.4.2_38
CVE-2013-1476
High February 2, 2013 2/2/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update38
<= 1.4.2_40
== 1.4.2_38
CVE-2013-1478
High February 2, 2013 2/2/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update38
<= 1.4.2_40
== 1.4.2_38
CVE-2013-1479
High February 2, 2013 2/2/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
CVE-2013-1480
High February 2, 2013 2/2/13
== 1.7.0-update9
== 1.7.0-update6
== 1.7.0-update3
== 1.7.0-update10
== 1.7.0-update11
== 1.7.0-update2
== 1.7.0-update5
== 1.7.0-update4
== 1.7.0
== 1.7.0-update7
== 1.7.0-update1
== 1.6.0-update30
== 1.6.0-update32
== 1.6.0-update35
== 1.6.0-update25
== 1.6.0-update33
== 1.6.0-update24
== 1.6.0-update26
== 1.6.0-update27
== 1.6.0-update22
== 1.6.0-update31
== 1.6.0-update23
== 1.6.0-update38
== 1.6.0-update37
== 1.6.0-update34
== 1.6.0-update29
== 1.5.0-update36
== 1.5.0-update38
<= 1.4.2_40
== 1.4.2_38

Showing vulnerabilities for 3 products matching "jre". Each product has independent pagination.

Frequently Asked Questions

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.