Skip to content

← Public intelligence

Maven package

ro.pippo:pippo-core

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

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Critical, CVSS 9.8MavenPublished

    Pippo RCE Vulnerability

    CVE-2018-18240 · GHSA-h892-x453-86wc

    Affected
    • Maven ro.pippo:pippo-core <= 1.11.0
    Fixed in
    1.12.0· Vendor fix available
    Issue
    Pippo through 1.11.0 allows remote code execution via a command to java.lang.ProcessBuilder because the XstreamEngine component does not use XStream's available protection mechanisms to restrict unmarshalling.

    Recommended action: Upgrade to 1.12.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Critical, CVSS 9.8MavenPublished

    Improper Restriction of XML External Entity Reference in pippo-core

    CVE-2018-20059 · GHSA-rmm5-g63h-m6g9

    Affected
    • Maven ro.pippo:pippo-core < 1.12.0
    Fixed in
    1.12.0· Vendor fix available
    Issue
    jaxb/JaxbEngine.java in Pippo 1.11.0 allows XXE.

    Recommended action: Upgrade to 1.12.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Critical, CVSS 9.8MavenPublished

    Deserialization of Untrusted Data in Pippo

    CVE-2018-18628 · GHSA-7fm6-2qw4-g3x3

    Affected
    • Maven ro.pippo:pippo-core < 1.12.0
    Fixed in
    1.12.0· Vendor fix available
    Issue
    An issue was discovered in Pippo 1.11.0. The function SerializationSessionDataTranscoder.decode() calls ObjectInputStream.readObject() to deserialize a SessionData object without checking the object types. An attacker can create a malicious object, base64 encode it, and place it in the PIPPOSESSION field of a cookie. Sending this cookie may lead to remote code execution.

    Recommended action: Upgrade to 1.12.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →