CVE-2016-20104 EyeLock CVE debrief

Who should care

Defenders responsible for EyeLock nano NXT devices should assess exposure and prioritize remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify the presence of affected versions, restrict access to the logdownload.php script, and implement input validation and sanitization for the 'path' parameter.

Why it matters

CVE-2016-20104 is a path traversal vulnerability in EyeLock nano NXT versions 3.05.1193, 3.04.1108, 3.03.944, and 3.01.646. The vulnerability allows unauthenticated attackers to read arbitrary files via the 'path' parameter in logdownload.php. Defenders should assess exposure, prioritize remediation, and verify the effectiveness of compensating controls.

• Verify the presence of affected EyeLock nano NXT versions
• Restrict access to the logdownload.php script
• Implement input validation and sanitization for the 'path' parameter
• Monitor for potential exploitation attempts

Technical summary

The EyeLock nano NXT versions 3.05.1193, 3.04.1108, 3.03.944, and 3.01.646 contain a path traversal vulnerability in the logdownload.php script. The vulnerability allows unauthenticated attackers to read arbitrary files via the 'path' parameter. To address this vulnerability, defenders should assess exposure, prioritize remediation, and verify the effectiveness of compensating controls. The vulnerability was first observed by the Shadowserver Foundation on 2023-10-19. Defenders should prioritize verifying the presence of affected EyeLock nano NXT versions and restrict access to the logdownload.php script.

Defensive priority

Defenders should prioritize verifying the presence of affected EyeLock nano NXT versions and restrict access to the logdownload.php script.

Recommended defensive actions

• Verify the presence of affected EyeLock nano NXT versions in the environment
• Restrict access to the logdownload.php script
• Implement input validation and sanitization for the 'path' parameter
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability was first observed by the Shadowserver Foundation on 2023-10-19. The CVE record and source item provide details about the vulnerability, affected versions, and potential exploitation.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.