CVE Tools

CVE-2015-3158

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 ...

No known exploitation. EPSS puts it in the 80th percentile. Fixed in 2.7.1.Final.

Published Updated Sources: CVE.org, NVD, GitHub

What to do

Find your product and version, then upgrade to the build on the right.

  • Maven org.picketlink:picketlink-tomcat-commonAffected: < 2.7.1.FinalUpgrade to: 2.7.1.FinalStated by: GitHub advisory
  • PicketlinkAffected: ≤ 2.7.0Upgrade to: after 2.7.0Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

PicketLink does not properly check role based authorization

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS80th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.9% chance of exploitation activity in the next 30 days, which ranks it in the 80th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

5 events over 3956 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availablerecord updated
  3. Publishedweakness classified

Affected products

Technical detail

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

Scored 4.0 by NVD.

How it is reached

  • Access Vector NetworkExploitable remotely over the network
  • Access Complexity LowNo special conditions required
  • Authentication SingleRequires single authentication

Impact if exploited

  • Confidentiality PartialSome information is disclosed
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Maven, not every advisory.