Skip to content

Commit 1abe3b9

Browse files
committed
Add detail to setup instructions
1 parent 297cbb2 commit 1abe3b9

File tree

1 file changed

+29
-7
lines changed

1 file changed

+29
-7
lines changed

documentation/modules/auxiliary/gather/checkpoint_gateway_fileread_cve_2024_24919.md

Lines changed: 29 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -12,16 +12,38 @@ tracked as CVE-2024-24919.
1212
Whether the read file's contents should be outputted to the console or stored as loot (default: false).
1313

1414
### TARGETFILE
15-
The target file to read (default: /etc/shadow). This should be a full Linux file path. Files containing binary data may not be read accurately.
15+
The target file to read (default: /etc/shadow). This should be a full Linux file path. Files containing binary data may
16+
not be read accurately.
1617

1718
## Testing
1819
To set up a test environment:
19-
1. Download an affected version of Check Point Security Gateway (Such as Check_Point_R81.20_T631.iso, SHA1: 42e25f45ab6b1694a97f76ca363d58040802e6d6).
20-
2. Install the ISO within a virtual machine.
21-
3. Browse to the administrator web dashboard on port 443 and complete the first-time setup tasks.
22-
4. On a Windows system, download and install a copy of Check Point SmartConsole, then use it to authenticate to Security Gateway.
23-
5. In SmartConsole, enable and configure the vulnerable Mobile Access or IPSec VPN blades.
24-
6. Publish and push the configuration changes to the device.
20+
1. Download an affected version of Check Point Security Gateway (Such as Check_Point_R81.20_T631.iso, SHA1:
21+
42e25f45ab6b1694a97f76ca363d58040802e6d6).
22+
1. Install the ISO within a virtual machine.
23+
1. Browse to the administrator web dashboard on port 443 and complete the first-time setup tasks.
24+
1. On a Windows system, download and install a copy of Check Point SmartConsole, then use it to authenticate to Security Gateway.
25+
1. In SmartConsole, enable and configure the vulnerable Mobile Access or IPSec VPN blades. These instructions focus on Mobile Access:
26+
1. Open the Gateway Properties:
27+
1. Navigate to Gateways & Servers in the left-hand menu.
28+
1. Select the gateway you want to configure.
29+
1. Right-click on the gateway and select Edit.
30+
1. Enable Mobile Access:
31+
1. In the General Properties tab, under Network Security, check the box for Mobile Access.
32+
1. Click on Mobile Access in the left-hand menu of the gateway properties window to access the Mobile Access settings.
33+
1. Configure Mobile Access:
34+
1. Set up the authentication methods under Authentication (e.g., LDAP, RADIUS, etc.).
35+
1. Configure the Portal Settings, specifying the URL for the Mobile Access Portal.
36+
1. Under Applications, define which applications and resources will be accessible via the Mobile Access portal.
37+
1. Click OK to close the properties window.
38+
1. Publish and push the configuration changes to the device.
39+
1. In SmartConsole, after completing your configuration, click on the Publish button at the top right corner of the
40+
SmartConsole window. This will save your changes to the management database.
41+
1. After publishing the changes, click on the Install Policy button located at the top of the SmartConsole window.
42+
1. In the Install Policy window, select the policy package you want to install. This is typically your main security policy package.
43+
1. Choose the gateways on which you want to install the policy. Make sure to select the gateway that you configured
44+
for Mobile Access and/or IPSec VPN.
45+
1. Click Install to begin the installation process. Once this process completes the gateway should then be vulnerable to this module.
46+
2547

2648
## Verification Steps
2749
1. Start msfconsole

0 commit comments

Comments
 (0)