Skip to main content

IBM and Red Hat Disclose Discovery of More Than 400 Java Vulnerabilities

IBM and Red Hat this week reported they have identified and remediated more than 400 previously unknown vulnerabilities in Java libraries since launching a Lightwell initiative earlier this year.

Additionally, Lightwell Clearinghouse, a program that enables IT organizations to submit specific open source software dependencies for priority review and remediation, is now generally available.

Ben Bread, a senior principal product manager for Red Hat, said the 400 unknown vulnerabilities represent twice the number that was expected to be uncovered and there will undoubtedly be more to come as artificial intelligence (AI) tools are used to analyze more legacy code.

Additionally, DevSecOps teams should expect a similar number of vulnerabilities to be discovered in libraries created using other programming languages, he added.

While IT teams are contracting with IBM and Red Hat to fix vulnerable code in their IT environments, the code fixes developed are being contributed back to upstream open source projects under responsible disclosure protocols.

IBM and Red Hat are not disclosing how many organizations are relying on them to help generate the code needed to remediate vulnerabilities in their legacy codebases, but they are delivered via secure repositories that connect to existing processes for building and deploying software. Via the Lightwell Network, IT teams can access verified patches, bring remediated software into their existing workflows and establish an ongoing process for addressing vulnerabilities. The more automated those processes are using best DevSecOps practices, the faster that remediation effort becomes, noted Bread.

In fact, the ongoing discovery of so many vulnerabilities in legacy code will prove to be a tipping point that spurs adoption of scanners and test automation platforms as the building and applying of patches becomes a more standard element of software engineering workflows, he added. Organizations that today require three months to validate a code fix are not going to be able to keep pace with the vulnerability deluge, noted Bread.

It’s not clear at what rate vulnerabilities are being exploited in the age of AI, but the assumption is cybercriminals will increasingly use AI models to both discover and exploit vulnerabilities in hours. As such, rather than patching software once a month to fix vulnerabilities, DevSecOps teams now need to be continuously patching software as more issues are continuously surfaced, said Bread.

Unfortunately, there are still many organizations that are not taking the threats AI poses to application security seriously enough, noted Bread. Many of those organizations will soon discover just how many vulnerabilities exist in codebases that many are assuming is more secure than it actually is. It’s only when organizations are able to preview the vulnerabilities and exploits that AI models are able to discover and create that the real scope of the issue becomes apparent, added Bread.

More challenging still, the cost of discovering a vulnerability is now as low as $30, so the economics of application security only continue to favor the attacker, he noted.

Hopefully, it won’t require some type of catastrophic event for more organizations to pay more attention to application security in the age of AI. The issue, of course, is that it’s not so much a question of when a breach will occur but rather how serious it is given the nature of the vulnerability being exploited.



from DevOps.com https://ift.tt/81A2UYh

Comments

Popular posts from this blog

One Year Later: How U.S. Winemakers Averted Disaster

One Year Later: How U.S. Winemakers Averted Disaster By Eric Asimov from NYT Food https://ift.tt/32fgBqf Wines, Shutdowns (Institutional), Layoffs and Job Reductions, Quarantine (Life and Culture)

The Agent Failure Your Approval Gate Can’t Catch

An agent that does the wrong thing leaves evidence — a bad diff, a malformed record, a customer complaint. An agent that does nothing and reports success leaves a green checkmark, and green is the one signal your incident process is built to trust. Worry more about the second failure, because everything a DevOps team owns for catching failure — exit codes, run status, alert rules, the dashboard itself — is instrumentation built for software that fails loudly. None of it fires when the failure is an absence. Andrew Filev made the strongest version of the reliability argument in these pages in July ( https://devops.com/reliability-comes-from-the-system-not-the-agent/ ): reliability is a property of the system, not the agent. “Reliability has rarely come from any single component in isolation,” he wrote. “It comes from how systems handle failure.” Aviation does not assume perfect pilots and hospitals do not assume perfect surgeons; both wrap imperfect actors in app...

Future Proofing the Foundation for AI-Ready Security Operations

Last December, the International Telecommunication Union (ITU), the United Nations’ (UN) body for information and communication technologies, supported  Open Cybersecurity Schema Framework (OCSF)  for ratification as an international standard by June 2026. Standardization is now a global necessity as governments worldwide integrate ITU standards into their national cybersecurity policies. First, What is OCSF? The OCSF provides a standardized approach to streamline security operations, improve threat detection, and accelerate incident response. This unlocks the full potential of security data. A standardized schema for security events normalizes data from various sources, which creates a unified foundation for advanced analytics and AI-powered tools. This standardization is crucial for unleashing the full potential of generative AI in cybersecurity, allowing organizations to better identify patterns and correlations across disparate data sources. Data Standardiza...