You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I doubt that im the first to report this, but my Defender for Endpoint has detected a vulnerability in Greenshot related to a dependency called Pippo.
Does anyone know for what purpose Pippo is being used? Im trying to determine the current risk and impact. If the exploit relies on a malicious payload, then the only thing I can think of is a user installing a faulty update. However its possible that the vulnerable code is not even being used by Greenshot.
Summary:
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.
The text was updated successfully, but these errors were encountered:
Hi,
I doubt that im the first to report this, but my Defender for Endpoint has detected a vulnerability in Greenshot related to a dependency called Pippo.
Does anyone know for what purpose Pippo is being used? Im trying to determine the current risk and impact. If the exploit relies on a malicious payload, then the only thing I can think of is a user installing a faulty update. However its possible that the vulnerable code is not even being used by Greenshot.
See:
pippo-java/pippo#643
Summary:
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.
The text was updated successfully, but these errors were encountered: