Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
- Issues: - SCS14 is allowed on encrypted connection (osdpphy.c) - No validation for RMACI is only in response to osdpSCRYPT (osdpcp.c) - Couldn't find anything specific in the OSDP specifications indicating it is forbidden, I'm gussing it shouldn't be allowed according from the secure connection initialization flow (let me know if you think there is spec-rela ted change that should be done) - Attack: - Once RMACI message can be sent during a session, attacker with MITM access to the communication may intercept the original RMACI reply and save it. - While the session continues, the attacker will record all of the replies and save them, till capturing the message to be replied (can be detected by ID, length or time based on inspection of visual activity next to the reade r) - Once attacker captures a session with the message to be replayed, he stops reseting the connection and waits for signal to perform the replay to of the PD to CP message (ex: by signaling remotly to the MIMT…
Recommended action: Upgrade to 3.0.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Issue: At ospdcommon.c, on the osdpreplyname function, any reply id between REPLYACK and REPLYXRD is valid, but names array do not declare all of the range. On a case of an undefined reply id within the range, name will be null (name = names[replyid - REPLYACK];). Null name will casue a crash on next line: if (name[0] == '\0') as null[0] is invalid. Attack: As this logic is not limited to a secure connection, attacker may trigger this vulnerability without any prior knowledge. Impact Denial of Service Patch The issue has been patched in 24409e98a260176765956ec766a04cb35984fab1
Recommended action: Upgrade to 2.4.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.