NginxDay - Lacework

NginxDay

Lacework Labs Advisory

Lacework Labs

April 15, 2022

Lacework Labs Advisory – “Nginx Day”

NginxDay“Nginx Day”, a zero day targeting Nginx was announced by “AgainstTheWest” via their Twitter account. On April 11th, 2022 a Github repository containing information about the vulnerability was released. At the time of this writing, it appears that this vulnerability is within LDAP integration modules (nginx-ldap-auth) which can be co-deployed with Nginx to enable LDAP authentication against services such as Jenkins, Gitlab,etc. and not with Nginx itself. Per Nginx’s  blog post, disabling Nginx’s ldapDaemon configuration can prevent the exploitation of this vulnerability. A discussion occurring on this Github issue created on AgainstTheWest’s NginxDay Github repo points to Bitnami’s 3rd party modules that enable LDAP support with Nginx as well as an issue of LDAP injection created on Nginx’s nginx-ldap-auth repo on January 10th. 

On Apr 11, 2022 Nginx published a public advisory that both the Open Source and Premium (Nginx Plus) versions are not affected. The security vulnerabilities lie in the Nginx LDAP reference implementation, which if you are using, Nginx has provided configurations to mitigate this vulnerability. At the time of this reporting, no CVE has been assigned to this vulnerability.  

According to the Nginx security advisory, the LDAP reference implementation is published as a Python daemon. While the exploit details are currently unclear, it’s presumed that an externally facing daemon would indicate exposure. Lacework Labs performed an analysis of cloud environments we monitor and only uncovered a few instances of this daemon over the past year and have reached out to those who are potentially affected. This indicates a low surface area risk relative to what we observed with Log4j. The following image is an example Lacework event showing reconnaissance against an exposed Nginx LDAP reference implementation. (SSH tag describes the indicator – not the activity):


NGNX Alert
Figure 1. Example Event – Recon against python daemon

Fazit

In the days of logos and brand names for vulnerabilities, it’s very easy to get caught up in a vicious cycle of never-ending panic. However, collecting available information from the source (Ex: a project’s security announcement page) and identifying what’s known and what’s unknown can help prioritize business decisions and avoid constantly having your SOC burn weekends. Keeping up to date with the countless CVEs is an endless battle. Leveraging vulnerability scanning for hosts, applications, and containers in addition to understanding your public-facing exposure is critical for prioritizing patching decisions.

For content like this and more, be sure to follow us on LinkedIn and Twitter!