dbcve.org
MojarraApplication · Oracle

CVE-2010-4007

MEDIUM · 5.0 CVSS v2.0 Published 2010-10-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Oracle Mojarra uses an encrypted View State without a Message Authentication Code (MAC), which makes it easier for remote attackers to perform successful modifications of the View State via a padding oracle attack, a related issue to CVE-2010-2057.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Oracle Mojarra (JavaServer Faces) encrypts the View State but omits a Message Authentication Code (MAC), allowing attackers to exploit padding oracle attacks to decrypt or modify the View State. This breaks the confidentiality and integrity of JSF application state, enabling remote attacks without authentication in some configurations.

MitigationEnable View State validation with MAC protection in Mojarra configuration or upgrade to a patched version that includes MAC-based integrity verification. Consider using server-side state saving with proper cryptographic protections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MojarraApplication
Affected:= 1.1= 1.1_02= 1.2= 1.2_01= 1.2_02= 1.2_03= 1.2_04= 1.2_05= 1.2_06= 1.2_07= 1.2_08= 1.2_09

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Mojarra version
    Locate the mojarra JAR file in your application lib directory or application server library (typically named mojarra-*.jar or jsf-impl.jar). Check the manifest file inside the JAR or the filename itself for the version number.
    Affected if The installed version matches one of: 1.1, 1.1_02, 1.2, 1.2_01, 1.2_02, 1.2_03, 1.2_04, 1.2_05, 1.2_06, 1.2_07, 1.2_08, or 1.2_09.
  2. Verify View State encryption is enabled
    Examine the web.xml deployment descriptor for JSF applications. Look for the context parameter named 'javax.faces.STATE_SAVING_METHOD' with value 'client'. Also check for any Mojarra-specific encryption parameters such as 'javax.faces.DEFAULT_SUFFIX' or custom ViewState encryption settings.
    Affected if Client-side state saving is configured (STATE_SAVING_METHOD set to 'client') which causes View State to be sent to the client in encrypted form.
  3. Confirm MAC validation is absent
    Check the Mojarra configuration files (faces-config.xml or web.xml) for the presence of the 'javax.faces.ENABLE_VIEWSTATE_MAC' parameter. If this parameter is missing or set to 'false', MAC protection is not enabled. Also look for any MAC-related configuration in server-specific JSF settings.
    Affected if The parameter 'javax.faces.ENABLE_VIEWSTATE_MAC' is either absent from configuration or explicitly set to false, meaning no Message Authentication Code is being generated for the View State.
  4. Inspect View State in transit
    Deploy a test JSF application using the affected version and submit a form. Capture the network traffic or inspect the hidden 'javax.faces.ViewState' input field in the HTML response. If the View State value appears as a long encrypted string (Base64 encoded) rather than a short server-side identifier, encryption is active.
    Affected if The View State value is a client-side encrypted payload (typically Base64 encoded) and the server is not using server-side state saving with MAC protection.

You are affected if your Mojarra version is 1.1.x or 1.2.x through 1.2_09 AND client-side state saving is enabled without MAC protection configured on the View State.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable View State validation with MAC protection in Mojarra configuration or upgrade to a patched version that includes MAC-based integrity verification. Consider using server-side state saving with proper cryptographic protections.

Fix this in Mojarra Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-4007 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-4007 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data