CVE-2025-68160

4.7 MEDIUM

📋 TL;DR

This vulnerability in OpenSSL's line-buffering BIO filter allows heap-based out-of-bounds writes when processing large, newline-free data with short writes in the BIO chain. It primarily affects third-party applications that explicitly use the BIO_f_linebuffer filter with attacker-controlled data, potentially causing crashes and denial of service. The vulnerability is assessed as low severity due to the unlikely combination of required conditions.

💻 Affected Systems

Products:
  • OpenSSL
Versions: OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1, 1.0.2
Operating Systems: All operating systems using affected OpenSSL versions
Default Config Vulnerable: ✅ No
Notes: BIO_f_linebuffer filter is not used by default in TLS/SSL data paths. In OpenSSL command-line applications, it's typically only pushed onto stdout/stderr on VMS systems. FIPS modules are not affected.

📦 What is this software?

Openssl by Openssl

OpenSSL is a robust, commercial-grade toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols. It provides cryptographic functions and is one of the most widely used libraries for implementing secure communications in applications worldwide.

Learn more about Openssl →

Openssl by Openssl

OpenSSL is a robust, commercial-grade toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols. It provides cryptographic functions and is one of the most widely used libraries for implementing secure communications in applications worldwide.

Learn more about Openssl →

Openssl by Openssl

OpenSSL is a robust, commercial-grade toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols. It provides cryptographic functions and is one of the most widely used libraries for implementing secure communications in applications worldwide.

Learn more about Openssl →

Openssl by Openssl

OpenSSL is a robust, commercial-grade toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols. It provides cryptographic functions and is one of the most widely used libraries for implementing secure communications in applications worldwide.

Learn more about Openssl →

Openssl by Openssl

OpenSSL is a robust, commercial-grade toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols. It provides cryptographic functions and is one of the most widely used libraries for implementing secure communications in applications worldwide.

Learn more about Openssl →

Openssl by Openssl

OpenSSL is a robust, commercial-grade toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols. It provides cryptographic functions and is one of the most widely used libraries for implementing secure communications in applications worldwide.

Learn more about Openssl →

Openssl by Openssl

OpenSSL is a robust, commercial-grade toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols. It provides cryptographic functions and is one of the most widely used libraries for implementing secure communications in applications worldwide.

Learn more about Openssl →

⚠️ Risk & Real-World Impact

🔴

Worst Case

Memory corruption leading to application crash and denial of service, potentially allowing arbitrary code execution if the memory corruption can be controlled by an attacker.

🟠

Likely Case

Application crash and denial of service in specific configurations where BIO_f_linebuffer is used with attacker-controlled data and short writes occur.

🟢

If Mitigated

No impact if BIO_f_linebuffer is not used, or if applications don't process attacker-controlled data through this filter with short writes.

🌐 Internet-Facing: LOW - Requires specific BIO_f_linebuffer usage with attacker-controlled data, which is uncommon in internet-facing applications.
🏢 Internal Only: LOW - Same constraints apply; requires specific configurations unlikely in most internal applications.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: NO
Unauthenticated Exploit: ✅ No
Complexity: HIGH

Exploitation requires: 1) Application explicitly uses BIO_f_linebuffer filter, 2) BIO chain performs short writes, 3) Large, newline-free attacker-controlled data, 4) These conditions under attacker control - making exploitation unlikely.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Patches available via the provided GitHub commit references

Vendor Advisory: https://github.com/openssl/openssl/commit/384011202af92605d926fafe4a0bcd6b65d162ad

Restart Required: Yes

Instructions:

1. Update OpenSSL to a patched version. 2. Recompile any applications linked against OpenSSL. 3. Restart affected services. 4. Verify the fix using version checks.

🔧 Temporary Workarounds

Disable BIO_f_linebuffer usage

all

Avoid using the BIO_f_linebuffer filter in applications, especially with untrusted data

Review application code and remove BIO_f_linebuffer usage where possible

Input validation and size limits

all

Implement input validation and size limits for data processed through BIO chains

Implement application-level input validation and size restrictions

🧯 If You Can't Patch

  • Avoid using BIO_f_linebuffer filter in applications
  • Implement strict input validation and size limits for data processed through BIO chains

🔍 How to Verify

Check if Vulnerable:

Check OpenSSL version with 'openssl version' and verify if it's in the affected version range

Check Version:

openssl version

Verify Fix Applied:

Verify OpenSSL version is updated beyond vulnerable versions and check for the specific commit fixes in the build

📡 Detection & Monitoring

Log Indicators:

  • Application crashes or segmentation faults in processes using OpenSSL BIO_f_linebuffer
  • Memory corruption errors in application logs

Network Indicators:

  • Sudden service unavailability of applications using OpenSSL

SIEM Query:

Process crashes with OpenSSL library in stack trace OR Application logs containing 'segmentation fault' with OpenSSL context

🔗 References

📤 Share & Export