Patch & vulnerability status
CHIRP-legacy 20221217
Latest tracked version 20221217. Release status, tracked CVEs, and automated cross-platform patching for CHIRP-legacy.
| Platform | Latest version | CVEs tracked | Last checked |
|---|---|---|---|
| Windows | 20221217 | 0 | 2024-12-06 |
Why keeping CHIRP-legacy patched matters
Unpatched third-party applications are one of the most common ways attackers get in: 57% of breached MSP clients and 32% of ransomware cases trace back to a missing patch. Every CHIRP-legacy release that fixes a security bug is public, so attackers see it too, and an out-of-date install becomes a documented way in. Tracking the installed version on every machine and closing the gap quickly is what turns a disclosed CVE into a non-event.
How Lavawall® patches CHIRP-legacy
Lavawall® watches CHIRP-legacy releases and CVEs continuously, ranks each update by risk, and deploys it across your whole fleet, Windows, macOS, and Linux, from a single agent, independently of your RMM. You get one place to see which machines are behind on CHIRP-legacy, one policy to bring them current, and timestamped evidence for audits.
Frequently asked questions
Lavawall tracks CHIRP-legacy at version 20221217 (last checked 2024-12-06). New releases are monitored continuously and can be deployed automatically across your fleet.
Lavawall continuously monitors CHIRP-legacy for newly disclosed CVEs and remediates them automatically as they appear.
Deploy the Lavawall® agent and CHIRP-legacy updates are applied automatically across Windows, macOS, and Linux, risk-ranked and reported, independently of your RMM.
Lavawall® monitors releases and CVEs for CHIRP-legacy through public information and proprietary statistical analysis, and can patch it automatically across your fleet.