Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Whisper this, but Java deserialisation vulnerability affects more libraries

The ‘challenge is internally written software’, says ISC

A Java deserialisation vulnerability may affect as many as 40 more software libraries than first feared, research has revealed this week.

The deserialisation bug in Apache Commons Collections affects popular distributed software such as WebSphere and JBoss, FoxGlove Security advised last month.

But new research by security-tools-for-software-developers firm SourceClear, out this week, suggests 40 additional libraries may be affected by the same bug.

Libraries including Apache Directory API, JMS Transport, versions of Webx All-in-one Bundle, hadoop-mapreduce-client-core, and many more appear to be at risk.

“What makes this flaw so nasty is that it is not a flaw in Java itself, but instead a flaw in a widely used library,” Johannes Ullrich, CTO at the SANS Institute Internet Storm Center, said at the time of the original warnings last month. “Inventorying which libraries are used by which specific software is notoriously difficult.”

“Several major enterprise software packages have been updated as a result. But the real challenge is internally written software, or custom software procured from third parties,” he added.

The problem has been understood for a while, but avoided much attention until last month when a more credible attack scenario was outlined. The root cause of the problem is down to apps not validating or checking untrusted input prior to deserialisation.

The vulnerability might be exploited by hackers to take control of app servers running affected libraries. The issue at the heart of the problem affects all apps that accept serialised Java objects.

Developers ought to review their code and libraries to see whether or not their technology might be vulnerable to the deserialisation vulnerability, SourceClear advises. ®

 

Similar topics

TIP US OFF

Send us news


Other stories you might like