Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2015-3158

PicketLink: PicketLink IDP ignores role based authorization

Overview

Published
26 Aug 2015
Modified
6 May 2026
Medium CVE
1 Registry packages
78 OS packages
1 Linux distributions
Yes Fix available

Description

The invokeNextValve function in identity/federation/bindings/tomcat/idp/AbstractIDPValve.java in PicketLink before 2.8.0.Beta1 does not properly check role based authorization, which allows remote authenticated users to gain access to restricted application resources via a (1) direct request or (2) request through an SP initiated flow.

Source: OX vulnerability database

Severity

4 · MEDIUM

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Low
Authentication
Single
Confidentiality
Partial
Integrity
None
Availability
None

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

Weakness: CWE-264

Affected packages · 1

Packages affected by CVE-2015-3158
EcosystemPackageVulnerableFixed in
Maven org.picketlink:picketlink-tomcat-common <2.7.1.Final 2.7.1.Final

Open a package to see all its vulnerabilities.

Operating systems · 11 fixes

Red Hat 1 release · 11 packages

fixed 11
jboss-modules glassfish-jsf-eap6 resteasy hornetq picketlink-bindings jboss-as-console +5
Red Hat fixes for CVE-2015-3158
ReleasePackageFixed inAdvisory
7 jboss-modules 0:1.3.7-1.Final_redhat_1.1.ep6.el7 RHSA-2015:1671
7 glassfish-jsf-eap6 0:2.1.28-9.redhat_10.1.ep6.el7 RHSA-2015:1671
7 resteasy 0:2.3.12-1.Final_redhat_1.1.ep6.el7 RHSA-2015:1671
7 hornetq 0:2.3.25-4.SP3_redhat_1.1.ep6.el7 RHSA-2015:1671
7 picketlink-bindings +1 0:2.5.4-8.SP7_redhat_1.1.ep6.el7 RHSA-2015:1671
7 jboss-as-console +1 0:2.5.6-2.Final_redhat_2.1.ep6.el7 RHSA-2015:1671

5 more rows

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.