Can anyone suggest the procedure to remediate the Java Deserialization Vulnerability?
First that ID points to this link: What Do WebLogic, WebSphere, JBoss, Jenkins, OpenNMS, and Your Application Have in Common? This Vulnerability.
First it looks like your going to need a patch in any case. Now the first thing I would look at doing if you don't have a patch is can you reduce the attack surface further either block the port or limit the IPs that can get too the service. If you are on linux you should be able to do this with something like iptables.
Now if your on a windows system I might have something that could help; the issue will still be detected and would not stop someone from executing an exploit but the exploit may not run or at least not at a high privilege.
I would also try to ensure that your application server is running as a limited user this will also help to lessen the impact should one happen.
Let me know if your on windows and I will try on the other method.
I would try the items referenced in the link below as a last resort and only in test as it could leave things in an unstable state.
if you provide the CVE perhaps I can do a little research on it and see.
Hello The QID is 11837, we are unable to track exact CVE ID.
We are on Windows system.
Hello We are also facing same issue relating to Java Deseialization. The QID is 11837, we are unable to track exact CVE ID.
We had a support case open for QID 11837 Java Deserialization for 4 months. Towards the end, we just wanted Support to tell us where Qualys was detecting and they could not. We finally had to do a PCAP and ask if they can verify the results. When support finally verified the location, the asset got decommissioned and it could not be remediated. So we were never able to fix it.
Our issue with it ended up being an IBM install of Java if that helps.
Retrieving data ...