Security

The Log4Shell vulnerability: what a website owner should do

The Log4j flaw disclosed on 9 December put IT teams worldwide on alert. Is your site affected, what to check, and when it is fine to stay calm.

The Log4Shell vulnerability: what a website owner should do

On 9 December 2021 a critical vulnerability (CVE-2021-44228, "Log4Shell") was disclosed in Apache Log4j, a widely used Java library. It is very easy to exploit: an attacker sends a specially crafted string, and if the application writes it to a log, code can be executed remotely. Within days the news was everywhere.

Is my website affected?

Most likely not. Log4j is a Java library. WordPress, Laravel and other PHP sites, as well as plain HTML sites, do not use it. But Java programs may run around your site:

  • search engines (for example Elasticsearch, Solr);
  • corporate software, payment and inventory systems, admin panels of network devices;
  • game servers (for example Minecraft);
  • "black box" services supplied by third parties.

What to do: a simple checklist

  1. Write down what you use. Website, hosting, email, CRM, payments — what software is behind each one?
  2. Ask your suppliers. Most large vendors have already published official statements. Get the answer in writing.
  3. Update. If you run Log4j yourself, move to 2.17.0 or newer. The first fix, 2.15.0, turned out to be incomplete, so check the exact version.
  4. Check your logs. Unusual ${jndi: strings are a sign of an attack attempt.
  5. Change passwords if you have seen suspicious activity.

A protective layer helps, but it is not the fix

Web application firewalls (WAF) block most attack attempts before they reach the site; rules for this flaw were published right away. But this is a temporary shield: the real fix is updating the vulnerable version.

What this episode teaches

The scale of the problem comes from the fact that many people do not know which libraries are inside their software. A useful habit for any business: keep a list of the systems you use, apply updates on time, and make sure your backup really works.

FAQ

Is my WordPress site at risk? Not from Log4Shell. But WordPress itself and its plugins should be kept up to date as well.

What should I do on shared hosting? The hosting provider looks after the server software; you only need to update your own part of the site.

If you would like your site and server checked, contact us through the client area.

Found it useful? Share it:

Get new articles by email

One or two emails a month: practical tips on websites, hosting and security. Unsubscribe any time with one click.