Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE-2018-18240 - Vulnerability in Pippo dependency? #539

Closed
cwings-dvb opened this issue May 16, 2024 · 2 comments
Closed

CVE-2018-18240 - Vulnerability in Pippo dependency? #539

cwings-dvb opened this issue May 16, 2024 · 2 comments

Comments

@cwings-dvb
Copy link

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.

@cwings-dvb
Copy link
Author

Someone in pippo-java/pippo#643 said that the Defender detection is a false-positive.

"Greenshot is a .NET application and doesn't use Java or Pippo, this can only be a false positive from defender."

I guess I lack the knowledge on how to check this for myself. Ill close the issue.

@jklingen
Copy link
Member

JFYI: it took quite some time, but it seems that the false positive has been fixed in Defender.
Thanks for reporting, anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants