First published: Mon Oct 03 2016(Updated: )
`CoreResponseStateManager` in Apache MyFaces Trinidad 1.0.0 through 1.0.13, 1.2.x before 1.2.15, 2.0.x before 2.0.2, and 2.1.x before 2.1.2 might allow attackers to conduct deserialization attacks via a crafted serialized viewstate string.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.apache.myfaces.trinidad:trinidad | >=2.1.0<2.1.2 | 2.1.2 |
maven/org.apache.myfaces.trinidad:trinidad | >=2.0.0<2.0.2 | 2.0.2 |
maven/org.apache.myfaces.trinidad:trinidad | >=1.2.0<1.2.15 | 1.2.15 |
maven/org.apache.myfaces.trinidad:trinidad | >=1.0.0<=1.0.13 | |
Apache MyFaces | >=1.0.0<1.0.13 | |
Apache MyFaces | >=1.2.0<1.2.15 | |
Apache MyFaces | >=2.0.0<2.0.2 | |
Apache MyFaces | >=2.1.0<2.1.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-5019 is classified as a medium severity vulnerability.
To fix CVE-2016-5019, upgrade Apache MyFaces Trinidad to version 1.2.15, 2.0.2, or 2.1.2 or later.
CVE-2016-5019 allows attackers to conduct deserialization attacks via a crafted serialized viewstate string.
CVE-2016-5019 affects Apache MyFaces Trinidad versions from 1.0.0 through 1.0.13, 1.2.x before 1.2.15, 2.0.x before 2.0.2, and 2.1.x before 2.1.2.
CVE-2016-5019 is related to the CoreResponseStateManager component in Apache MyFaces Trinidad.