CVE-2013-6447 redhat jboss seam 2 framework
redhat jboss seam 2 framework: no CVSS score yet. EPSS 2.7% estimated probability of exploitation activity in the next 30 days.
On this page
- EPSS
- 2.7% (unchanged from 2.7% a week ago; 2.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 86th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Patch: https://bugzilla.redhat.com/show_bug.cgi?id=1044784
- Vendor advisory: http://secunia.com/advisories/56572
- Vendor advisory: https://bugzilla.redhat.com/show_bug.cgi?id=1044784
Ask an AI about this CVE
Show the prompt
Explain CVE-2013-6447 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2013-6447?via=ask-ai-copy and https://cve.bz/cve/CVE-2013-6447?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2013-6447 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| redhat:jboss_seam_2_framework | through 2.3.1 |
| redhat:jboss_seam_2_framework | 2.0.0:beta1 |
| redhat:jboss_seam_2_framework | 2.0.0:cr1 |
| redhat:jboss_seam_2_framework | 2.0.0:cr2 |
| redhat:jboss_seam_2_framework | 2.0.0:cr3 |
| redhat:jboss_seam_2_framework | 2.0.0:ga |
| redhat:jboss_seam_2_framework | 2.0.1:cr1 |
| redhat:jboss_seam_2_framework | 2.0.1:cr2 |
| redhat:jboss_seam_2_framework | 2.0.1:ga |
| redhat:jboss_seam_2_framework | 2.0.2:cr1 |
| redhat:jboss_seam_2_framework | 2.0.2:cr2 |
| redhat:jboss_seam_2_framework | 2.0.2:ga |
| redhat:jboss_seam_2_framework | 2.0.2:sp1 |
| redhat:jboss_seam_2_framework | 2.0.3:cr1 |
| redhat:jboss_seam_2_framework | 2.1.0:alpha1 |
| redhat:jboss_seam_2_framework | 2.1.0:beta1 |
| redhat:jboss_seam_2_framework | 2.1.0:cr1 |
| redhat:jboss_seam_2_framework | 2.1.0:ga |
| redhat:jboss_seam_2_framework | 2.1.0:sp1 |
| redhat:jboss_seam_2_framework | 2.1.1:cr1 |
| redhat:jboss_seam_2_framework | 2.1.1:cr2 |
| redhat:jboss_seam_2_framework | 2.1.1:ga |
| redhat:jboss_seam_2_framework | 2.1.2 |
| redhat:jboss_seam_2_framework | 2.1.2:cr1 |
| redhat:jboss_seam_2_framework | 2.1.2:cr2 |
| redhat:jboss_seam_2_framework | 2.2.0:cr1 |
| redhat:jboss_seam_2_framework | 2.2.0:ga |
| redhat:jboss_seam_2_framework | 2.2.1 |
| redhat:jboss_seam_2_framework | 2.2.1:cr1 |
| redhat:jboss_seam_2_framework | 2.2.1:cr2 |
| redhat:jboss_seam_2_framework | 2.2.1:cr3 |
| redhat:jboss_seam_2_framework | 2.2.2 |
| redhat:jboss_seam_2_framework | 2.3.0 |
| redhat:jboss_seam_2_framework | 2.3.0:alpha |
| redhat:jboss_seam_2_framework | 2.3.0:beta1 |
| redhat:jboss_seam_2_framework | 2.3.0:beta2 |
| redhat:jboss_seam_2_framework | 2.3.0:cr1 |
| redhat:jboss_seam_2_framework | 2.3.1:cr1 |
Red Hat
Red Hat rates this Moderate.
This issue affects Seam 3 remoting, but Seam 3 is not shipped with any Red Hat products, and Seam 3 development has been terminated. This issue is not currently planned to be addressed in a future update to Seam 3.
Red Hat JBoss BRMS 5; Red Hat JBoss Enterprise Application Platform 4 and 5; Red Hat JBoss Enterprise Portal Platform 5; Red Hat JBoss Enterprise SOA Platform 4 and 5; and Red Hat JBoss Enterprise Web Platform 5 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat JBoss Web Framework Kit 2.4 | Seam | Fixed 2014-01-20 | RHSA-2014:0045 |
| Red Hat JBoss Enterprise Application Platform 5 | seam | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2013-6447.
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).