Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Information disclosure vulnerability in Apache MyFaces Core 2.0.1 through 2.0.10 and 2.1.0 through 2.1.4 allows remote attackers to inject EL expressions via crafted parameters.
Recommended action: Upgrade to 2.1.5 or 2.0.11 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
In the default configuration, Apache MyFaces Core versions 2.2.0 to 2.2.13, 2.3.0 to 2.3.7, 2.3-next-M1 to 2.3-next-M4, and 3.0.0-RC1 use cryptographically weak implicit and explicit cross-site request forgery (CSRF) tokens. Due to that limitation, it is possible (although difficult) for an attacker to calculate a future CSRF token value and to use that value to trick a user into executing unwanted actions on an application. Mitigation: Existing web.xml configuration parameters can be used to direct MyFaces to use SecureRandom for CSRF token generation: org.apache.myfaces.RANDOMKEYINVIEWSTATESESSIONTOKEN=secureRandom org.apache.myfaces.RANDOMKEYINCSRFSESSIONTOKEN=secureRandom org.apache.myfaces.RANDOMKEYINWEBSOCKETSESSIONTOKEN=secureRandom
Recommended action: Upgrade to 2.3.8, 2.2.14, 2.1.19 or 2.0.25 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.