# Lever: Apache Log4j2

- Impact (vendor’s label): major
- Status: resolved
- Started: 2021-12-13 20:25 UTC · Resolved: 2022-01-31 17:37 UTC · Duration: 49 d
- Updates: 1
- [Vendor status page: https://status.lever.co/incidents/4f6zkg8dl5lh](https://status.lever.co/incidents/4f6zkg8dl5lh)
- [Company: Lever](https://rewindex.com/company/lever.md)

## Timeline of updates

- **resolved** 2022-01-31 17:37 UTC: Lever is committed to the protection and safety of your data. We have adapted our approach as the log4j vulnerabilities evolved (CVE-2021-44228, CVE-2021-45046, and CVE-2021-45105). We have completed a full scan of our environment for vulnerable versions of log4j. We have upgraded 2 affected backend systems where vulnerable log4j has been found. We have added additional monitoring for the types of applications that may try to run vulnerable log4j libraries. We have tuned our security monitoring software to alert on behavior that would indicate a log4j compromise. We appreciate your trust in us as we continue to make your success our top priority. For more information, please review CVE-2021-44228, CVE-2021-45046, and CVE-2021-45105 and the Apache Log4j2 post.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/lever/incidents/4f6zkg8dl5lh · Markdown: https://rewindex.com/company/lever/incidents/4f6zkg8dl5lh.md · JSON: https://rewindex.com/api/v1/companies/lever/incidents/4f6zkg8dl5lh · Generated 2026-10-18T09:46:20.652Z