Apache Solr: code execution flaw under attack

What is affected

Apache Solr is mostly run by companies, schools and public bodies, not on home computers. You are unlikely to have it yourself, but organisations that hold your data may. Breaches that start with flaws like this one are how personal data ends up leaked.

The optional Apache Solr module DataImportHandler contains a code injection vulnerability.

What an attacker can do

This is a code execution flaw. It lets an attacker run their own commands or programs on the affected system. In practice that usually means taking it over: installing malware, stealing data or using it to reach other devices on the same network.

How it is reached

Over the internet or network

Access the attacker needs

An administrator account

Does the victim have to do something?

No, works without the victim doing anything

What to do

1. At home: nothing to install. Keep your own devices updated and use a different password for every service, so that a breach at one organisation does not open your other accounts.
2. If you administer Apache Solr at work: apply the vendor's fix or mitigation now and review logs for signs of compromise, because the flaw was being exploited before it was listed.
3. If the product is past its support date and no fix exists, take it off the internet or retire it.

Apply updates per vendor instructions.

How urgent is it

CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on December 10, 2021, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by June 10, 2022, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.

The EPSS model estimates a 84% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 99.7% of all scored vulnerabilities.

Its CVSS severity score is 7.2 out of 10 (high), as recorded in the US National Vulnerability Database.

Technical description

In Apache Solr, the DataImportHandler, an optional but popular module to pull in data from databases and other sources, has a feature in which the whole DIH configuration can come from a request's "dataConfig" parameter. The debug mode of the DIH admin screen uses this to allow convenient debugging / development of a DIH config. Since a DIH config can contain scripts, this parameter is a security risk. Starting with version 8.2.0 of Solr, use of this parameter requires setting the Java System property "enable.dih.dataConfigParam" to true.