There are now two different patch questions

Hotfix 2 remains N-able's fix for the internet-facing, unauthenticated issues in the first disclosure. The company says additional vulnerabilities disclosed on 12 November involve Legacy API abuse and agent impersonation. It says the Legacy API is off by default, and that the agent issue requires an attacker to have an endpoint foothold. N-able is preparing HF3 to tighten authentication and permissions, harden agent communication and remove Legacy API access.

On 13 November N-able published indicators relevant to customers whose Legacy API was enabled. It also said hosted environments had received temporary protections and the Intune integration had been turned off as a precaution. Reporting from BleepingComputer describes observed exploitation of the newly disclosed issue; N-able's public notice does not confirm a total number of compromised customer servers.

Do not equate HF2 with the planned HF3

N-able says HF2 addresses the earlier unauthenticated issues. Further fixes are still being developed. Keep the two disclosure sets separate in patch tickets and incident records.

Review configuration and evidence together

  1. 1

    Verify Legacy API state. Confirm it is disabled on each on-premises server. If it had been enabled, record the dates and use N-able's current indicators and logs to investigate that interval.

  2. 2

    Finish the HF2 rollout. Verify the server hotfix and continue the vendor's Agent-then-Probe upgrade order. Check hosted and on-premises responsibilities separately.

  3. 3

    Track further remediation. Watch N-able's HF3 guidance and validate any temporary integration changes before restoring them. Escalate suspicious server or endpoint activity through the incident process.

An indicator is evidence to test, not a clean bill

The vendor's network indicators are useful for a focused look back, especially where the Legacy API was active. A match warrants investigation; no match does not prove a server was untouched. Keep the original logs, configuration history and the scope of any managed customer access together.