projectcleanbeach.com

We strengthen the trust in the use of Open Source
By proactively detecting bugs before the bad guys find them

Understanding
the risk

Open Source contributions power 97% of enterprise code, with 77% of the total code base derived from Open Source.*

Historically, many serious vulnerabilities in applications stem from undetected weaknesses in this code. Well known critical bugs such as Heartbleed were lying quietly in the code for years. Heartbleed for 2 years, Log4Shell for 8 years!

*Source: 2024 Synopsys “Open Source Security and Risk Analysis” (OSSRA)

Why do these bugs lie dormant for so long waiting for some bad actor (or nation state) to exploit?

Discovered in 2014, this OpenSSL flaw allowed attackers to read sensitive data from affected servers. Undetected for over two years, it impacted 17% of secure web servers, costing companies an estimated $500 million in mitigation.

Found in October 2022 in the Apache Commons Text library, allows remote code execution through untrusted input. The root cause was hidden in the code for 4 years. It poses significant risks due to its widespread use in enterprise applications.
(IBM - United States)

A critical Log4j flaw, undetected from 2013 until December 2021 (8 years), allowed arbitrary code execution. The vulnerability's widespread impact prompted urgent global response, with potential costs running into billions due to its extensive use.

The Sudo buffer overflow vulnerability, disclosed in 2021, was hidden for nearly a decade. It allowed unprivileged users to gain root access on affected systems, leading to urgent patching due to the high risk and ease of exploitation.

PrintDemon is a Windows Print Spooler flaw allowing low-privileged users to gain SYSTEM privileges. It affects multiple Windows versions and was patched in the May 2020 update after being hidden in the code for 24 years. Its ease of exploitation posed significant security risks.

Current tools are inadequate

Existing analysis tools to scan and detect these bugs are currently unable to scale to the level needed to inspect the hundreds of thousands of Open Source projects. They are overwhelmed by the cost and complexity of processing vast amounts of warnings across numerous projects

Until now...

We Detect Bugs at Scale

Project Clean Beach uses powerful new analysis methods along with Artificial Intelligence to scan Open Source projects at scale.
Project Clean Beach is made possible by leveraging OpenRefactory’s Intelligent Code Repair (iCR). iCR excels by detecting bugs that other tools miss, thanks to its superior reach, efficiency, and AI assistance. It also dramatically reduces false positives, enabling the Project Clean Beach engineering team to find those undetected bugs by processing thousands of projects each month.

We support the Open Source community in 2 important ways

Cleaning Core Open Source Libraries

With support from the Alpha Omega Project—a consortium of Amazon, Microsoft, and Google—Project Clean Beach cleans widely-used libraries across popular languages like Java, Python, and Go. This enhances security for all developers relying on Open Source.

Ensuring Security Through SBOM Analysis

By joining Project Clean Beach, organizations can submit their Software Bill of Materials (SBOM) for analysis, ensuring their specific libraries and entire dependency chains are thoroughly checked for safety. This ensures that your code is fully secure.

As a participant in Project Clean Beach, you will get

In-Depth Risk Assessment
Comprehensive evaluation of potential risks with a unique signal to identify emerging security vulnerabilities in the supply chain before they escalate.
Dual-Faceted Risk Mitigation
Collaborative efforts with both the enterprise and open-source project maintainers to address and strengthen security measures from multiple angles.
Ongoing Vigilance
Regular updates reflecting the evolving risk landscape, ensuring that enterprises remain informed and prepared to handle new and emerging threats.
Scroll to Top