Saturday, February 8, 2025
HomeAnti VirusResearchers Found that Adobe Acrobat Blocking Security Software Visibility into PDF Files

Researchers Found that Adobe Acrobat Blocking Security Software Visibility into PDF Files

Published on

SIEM as a Service

Follow Us on Google News

Adobe Acrobat is blocking security software from inspecting the PDF files it opens. The end result of the work is the users are at risk since this decreases security.

Essentially, Adobe’s product blocks 30 security products from monitoring malicious activity by checking whether they are loaded into their processes.

Blocking Incompatible Antivirus Tools

Having visibility into all processes within a system is essential to a security tool for it to work efficiently. The dynamic linking libraries (DLLs) are developed to accomplish this by injecting them into software products that are launched by the system.

While apart from this, the cybersecurity researchers at Minerva Labs affirmed that, in the past, PDF files were used to execute the malware on a computer system through the use of malicious macros. 

The document can be amended by incorporating a PowerShell command in the ‘OpenAction’ section for the purpose of identifying the activities that are malicious. 

Here below we have mentioned the list of AV tools that are blocked by Adobe Acrobat:-

  • Trend Micro
  • BitDefender  
  • AVAST  
  • F-Secure 
  • McAfee 
  • 360 Security 
  • Citrix 
  • Symantec 
  • Morphisec 
  • Malwarebytes 
  • Checkpoint 
  • Ahnlab 
  • Cylance 
  • Sophos 
  • CyberArk 
  • Citrix 
  • BullGuard 
  • Panda Security 
  • Fortinet 
  • Emsisoft 
  • ESET 
  • K7 TotalSecurity 
  • Kaspersky 
  • AVG 
  • CMC Internet Security 
  • Samsung Smart Security ESCORT 
  • Moon Secure 
  • NOD32 
  • PC Matic 
  • SentryBay

Technical Analysis

This system query is accomplished using a CEF Dynamic Link Library called libcef.dll, which can be found in a wide range of programs that use this “dll” file.

Despite its short list of components that need to be blacklisted due to their potential for conflict, Chromium DLL users can modify and incorporate any DLL according to their needs.

Moreover, a pair of Adobe processes load the libcef.dll file, and here they are mentioned below:-

  • AcroCEF.exe
  • RdrCEF.exe

There are various checks Adobe performs under the registry key ‘SOFTWARE/Adobe/Adobe Acrobat/DC/DLLInjection/’, one of which is to determine if the bBlockDllInjection is set to 1.

While the DLLs created by antivirus products will be prevented from being injected into processes if it is implemented as such.

At the time of first launching Adobe Reader, the value of the registry key is ‘0’. However, it can be modified at any time thereafter. Depending on how your operating system performs or which version of Adobe Acrobat you have installed, this setting may vary.

Response of Adobe on the issue

Adobe has already asserted that they are receiving several reports from their users who are experiencing issues as a result of the CEF library in Adobe Acrobat being incompatible with its DLL components originating from some security products.

This problem has been acknowledged by Adobe and as a result, the company plans to work with these vendors to fix it.

You can follow us on LinkedinTwitterFacebook for daily Cybersecurity updates.

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

UK Pressures Apple to Create Global Backdoor To Spy on Encrypted iCloud Access

United Kingdom has reportedly ordered Apple to create a backdoor allowing access to all...

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...

Securing GAI-Driven Semantic Communications: A Novel Defense Against Backdoor Attacks

Semantic communication systems, powered by Generative AI (GAI), are transforming the way information is...

Cybercriminals Target IIS Servers to Spread BadIIS Malware

A recent wave of cyberattacks has revealed the exploitation of Microsoft Internet Information Services...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

UK Pressures Apple to Create Global Backdoor To Spy on Encrypted iCloud Access

United Kingdom has reportedly ordered Apple to create a backdoor allowing access to all...

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...

Securing GAI-Driven Semantic Communications: A Novel Defense Against Backdoor Attacks

Semantic communication systems, powered by Generative AI (GAI), are transforming the way information is...