New N-able N-central exploit code claims root access on servers with the latest hotfix
- Severity
- Critical
- Sources
- 1
What happened
Exploit code 4EverAble2Shell (reportedly requiring Legacy API mode) and Agent2Shell (targeting N-central server to Windows Agent and Probe communication, requiring knowledge of the appliance ID) reportedly bypasses the N-able hotfix released 10 November that addressed seven CVEs from the Able2Shell set. Huntress reports more than ten issues, with no vendor fix at its 12 November update. Defenders should take on-premises N-central offline or remove internet exposure, review logs for requests to /dms/services/ServerUI and /dms2/services2/ServerMMS2 with session ID -1, and check for unexpected script backups, a suspicious flagdefault.json symlink, encoded PowerShell from N-able components, Software Probe file changes and unexplained service restarts from 11 November onward. Treat HF2 as not proof of safety and run incident response across the appliance and managed endpoints.
For security analysts · Written by AI from 1 source · Wrong?
What to do
- Take on-premises N-central offline or remove its internet access, even after installing HF2, until a fix is available.
- Review N-central server logs for requests to /dms/services/ServerUI and /dms2/services2/ServerMMS2 using session ID -1.
- Follow N-able's status updates and start an incident response review covering the appliance and managed customer devices.
Written by AI from the sources, checked against them
Full story timeline · 1 update
Who reported · 1 outlet
Who and what is in it
Products