CVE-2008-1285 — jsf-api
MEDIUMCVE-2008-1285 is a medium-severity (CVSS 5.3) Cross-site Scripting (XSS) vulnerability in com.sun.faces:jsf-api. A fix is available for com.sun.faces:jsf-api — see the affected versions and patch details below.
Cross-site scripting (XSS) vulnerability in Sun Java Server Faces (JSF)
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2008-1285 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
com.sun.faces:jsf-apiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Cross-site scripting (XSS) vulnerability in Sun Java Server Faces (JSF) 1.2 before 1.2_08 allows remote attackers to inject arbitrary web script or HTML via unknown vectors.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.sun.faces:jsf-api | all versions | 1.2.08com.sun.faces:jsf-api:1.2.08 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.sun.faces:jsf-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.sun.faces:jsf-api to 1.2.08 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2008-1285 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2008-1285 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2008-1285. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| JBEAP 4.2.0 for RHEL 4 | glassfish-javamail-0:1.4.0-0jpp.ep1.9.el4 | RHSA-2008:0825 |
| JBEAP 4.2.0 for RHEL 5 | hibernate3-1:3.2.4-1.SP1_CP03.0jpp.ep1.1.el5 | RHSA-2008:0827 |
| Red Hat JBoss Enterprise Application Platform 4.3 for RHEL 4 | glassfish-javamail-0:1.4.0-0jpp.ep1.9.el4 | RHSA-2008:0826 |
| Red Hat JBoss Enterprise Application Platform 4.3 for RHEL 5 | asm-0:1.5.3-1jpp.ep1.2.el5 | RHSA-2008:0828 |
Frequently Asked Questions
Is CVE-2008-1285 in your dependencies?
O3 Security finds CVE-2008-1285 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.