Viktor Steinmann has reported a weakness in Check Point VPN-1 SecureClient, which potentially can be exploited by malicious users to bypass certain security restrictions.
The weakness is caused due to SecureClient relying on the local copy of the "local.scv" file downloaded from the policy server to perform client integrity checks before allowing the client to connect to the internal networks via VPN. This check may be bypassed by users with write-access to the file by continuously replacing it with a modified copy.
This weakness can potentially allow the SCV (Secure Configuration Verification) feature of the product to be bypassed, which allow client systems that are not compliant to the organisation's security policies to connect to the internal networks.
Solution: Do not rely on the SCV as the only means of ensuring that client systems are configured according to the security policy.
Provided and/or discovered by: Viktor Steinmann
Original Advisory: http://lists.grok.org.uk/pipermail/full-disclosure/2005-December/039634.html
Do you have additional information related to this advisory?
Please provide information about patches, mitigating factors, new versions, exploits, faulty patches, links, and other relevant data by posting comments to this Advisory. You can also send this
information to firstname.lastname@example.org
Subject: Check Point VPN-1 SecureClient Secure Configuration Verification Bypass Weakness
No posts yet
You must be logged in to post a comment.
Secunia Customer Login
Not a customer already?
Learn more about how our market leading Vulnerability Management solutions can help you manage risk and ensure compliance.