Skip to content
Fencer Intel
medium 5.0

CVE-2013-0449 json

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Update 11 allows remote attackers to…

published 13y ago modified 4mo ago also EUVD-2013-0460

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.8%
EPSS 3.8% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Update 11 allows remote attackers to affect confidentiality via unknown vectors related to Deployment.

Patch / fix

  • java-1.7.0-ibm RHEL 5 EXTRAS 1:1.7.0.4.0-1jpp.2.el5_9
  • java-1.7.0-ibm RHEL 6 EXTRAS 1:1.7.0.4.0-1jpp.2.el6_4
  • java-1.7.0-ibm-src RHEL 5 EXTRAS 1:1.7.0.4.0-1jpp.2.el5_9
  • java-1.7.0-ibm-src RHEL 6 EXTRAS 1:1.7.0.4.0-1jpp.2.el6_4
  • java-1.7.0-ibm-demo RHEL 5 EXTRAS 1:1.7.0.4.0-1jpp.2.el5_9
  • java-1.7.0-ibm-demo RHEL 6 EXTRAS 1:1.7.0.4.0-1jpp.2.el6_4
  • java-1.7.0-ibm-jdbc RHEL 5 EXTRAS 1:1.7.0.4.0-1jpp.2.el5_9
  • java-1.7.0-ibm-jdbc RHEL 6 EXTRAS 1:1.7.0.4.0-1jpp.2.el6_4

red hat advisories RHSA-2013:0626RHSA-2013:0237

Is CVE-2013-0449 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-0449 updated cvss 4.3

JDK: unspecified vulnerability fixed in 7u13 (Deployment)

  • Red Hat Enterprise Linux 5 java-1.4.2-ibm
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux Desktop Supplementary (v. 6) java-1.7.0-ibm 1.7.0.4.0-1jpp.2.el6_4, java-1.7.0-oracle 1.7.0.13-1jpp.3.el6_3, java-1.7.0-ibm-src 1.7.0.4.0-1jpp.2.el6_4, java-1.7.0-ibm-demo 1.7.0.4.0-1jpp.2.el6_4, java-1.7.0-ibm-jdbc 1.7.0.4.0-1jpp.2.el6_4, java-1.7.0-oracle-src 1.7.0.13-1jpp.3.el6_3, +4 more Red Hat Enterprise Linux HPC Node Supplementary (v. 6) java-1.7.0-ibm 1.7.0.4.0-1jpp.2.el6_4, java-1.7.0-oracle 1.7.0.13-1jpp.3.el6_3, java-1.7.0-ibm-src 1.7.0.4.0-1jpp.2.el6_4, java-1.7.0-ibm-demo 1.7.0.4.0-1jpp.2.el6_4, java-1.7.0-oracle-src 1.7.0.13-1jpp.3.el6_3, java-1.7.0-oracle-javafx 1.7.0.13-1jpp.3.el6_3 Red Hat Enterprise Linux Server Supplementary (v. 5) java-1.7.0-ibm 1.7.0.4.0-1jpp.2.el5_9, java-1.7.0-oracle 1.7.0.13-1jpp.1.el5_9, java-1.7.0-ibm-src 1.7.0.4.0-1jpp.2.el5_9, java-1.7.0-ibm-demo 1.7.0.4.0-1jpp.2.el5_9, java-1.7.0-ibm-jdbc 1.7.0.4.0-1jpp.2.el5_9, java-1.7.0-oracle-src 1.7.0.13-1jpp.1.el5_9, +4 more Red Hat Enterprise Linux Server Supplementary (v. 6) java-1.7.0-ibm 1.7.0.4.0-1jpp.2.el6_4, java-1.7.0-oracle 1.7.0.13-1jpp.3.el6_3, java-1.7.0-ibm-src 1.7.0.4.0-1jpp.2.el6_4, java-1.7.0-ibm-demo 1.7.0.4.0-1jpp.2.el6_4, java-1.7.0-ibm-jdbc 1.7.0.4.0-1jpp.2.el6_4, java-1.7.0-oracle-src 1.7.0.13-1jpp.3.el6_3, +4 more Red Hat Enterprise Linux Workstation Supplementary (v. 6) java-1.7.0-ibm 1.7.0.4.0-1jpp.2.el6_4, java-1.7.0-oracle 1.7.0.13-1jpp.3.el6_3, java-1.7.0-ibm-src 1.7.0.4.0-1jpp.2.el6_4, java-1.7.0-ibm-demo 1.7.0.4.0-1jpp.2.el6_4, java-1.7.0-ibm-jdbc 1.7.0.4.0-1jpp.2.el6_4, java-1.7.0-oracle-src 1.7.0.13-1jpp.3.el6_3, +4 more
    fixed: vendor fix RHSA-2013:0626
  • Red Hat Enterprise Linux 5 java-1.5.0-ibm, java-1.6.0-ibm, java-1.6.0-sun, java-1.6.0-sun-src, java-1.6.0-sun-demo, java-1.6.0-sun-jdbc, +2 more Red Hat Enterprise Linux 6 java-1.5.0-ibm, java-1.6.0-ibm, java-1.6.0-sun, java-1.5.0-ibm-src, java-1.6.0-ibm-src, java-1.6.0-sun-src, +11 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.84% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.