You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Packs/CVE_2022_3786_and_CVE_2022_3602_-_OpenSSL_X.509_Buffer_Overflows/README.md
+10-8
Original file line number
Diff line number
Diff line change
@@ -4,22 +4,24 @@ On November 1, OpenSSL released a [security advisory](https://www.openssl.org/ne
4
4
5
5
The vulnerability described in CVE-2022-3602 allows an attacker to obtain a 4-byte overflow on the stack by crafting a malicious email address within the attacker-controlled certificate. The overflow will result in a crash (most likely scenario) or potentially remote code execution (much less likely). In CVE-2022-3786, an attacker can achieve a stack overflow of arbitrary length by crafting a malicious email address within the attacker-controlled certificate.
6
6
7
-
Both vulnerabilities are “triggered through X.509 certificate verification, specifically, name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer.”
7
+
Both vulnerabilities are “triggered through X.509 certificate verification, specifically, name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer.”
8
8
9
9
**The playbook includes the following tasks:**
10
+
10
11
* Hunting for active processes running OpenSSL vulnerable versions using:
11
-
* Cortex XDR
12
-
* Splunk
13
-
* Azure Sentinel
14
-
* Cortex Xpanse
15
-
* Prisma
16
-
* PANOS
12
+
* Cortex XDR
13
+
* Splunk
14
+
* Azure Sentinel
15
+
* Cortex Xpanse
16
+
* Prisma
17
+
* PANOS
17
18
18
19
**Mitigations:**
20
+
19
21
* OpenSSL official patch
20
22
21
23
More information:
22
24
23
25
[Unit42 Threat Brief: CVE-2022-3786 and CVE-2022-3602: OpenSSL X.509 Buffer Overflows](https://unit42.paloaltonetworks.com/openssl-vulnerabilities/)
Copy file name to clipboardExpand all lines: Packs/Envoy/Integrations/EnvoyIAM/README.md
+60-68
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,6 @@ This integration was integrated and tested with version v2 of Envoy SCIM API.
3
3
4
4
## Configure Envoy IAM in Cortex
5
5
6
-
7
6
|**Parameter**|**Description**|**Required**|
8
7
| --- | --- | --- |
9
8
| Base URL || True |
@@ -19,159 +18,152 @@ This integration was integrated and tested with version v2 of Envoy SCIM API.
19
18
| Outgoing Mapper || True |
20
19
21
20
## Commands
21
+
22
22
You can execute these commands from the CLI, as part of an automation, or in a playbook.
23
23
After you successfully execute a command, a DBot message appears in the War Room with the command details.
24
+
24
25
### iam-create-user
26
+
25
27
***
26
28
Creates a user.
27
29
28
-
29
30
#### Base Command
30
31
31
32
`iam-create-user`
33
+
32
34
#### Input
33
35
34
36
|**Argument Name**|**Description**|**Required**|
35
37
| --- | --- | --- |
36
-
| user-profile | User Profile indicator details. | Required |
37
-
| allow-enable | When set to true, after the command execution the status of the user in the 3rd-party integration will be active. Possible values are: true, false. Default is true. | Optional |
38
-
38
+
| user-profile | User Profile indicator details. | Required |
39
+
| allow-enable | When set to true, after the command execution the status of the user in the 3rd-party integration will be active. Possible values are: true, false. Default is true. | Optional |
39
40
40
41
#### Context Output
41
42
42
43
|**Path**|**Type**|**Description**|
43
44
| --- | --- | --- |
44
-
| IAM.Vendor.active | Boolean | When true, indicates that the employee's status is active in the 3rd-party integration. |
45
-
| IAM.Vendor.brand | String | Name of the integration. |
46
-
| IAM.Vendor.details | string | Provides the raw data from the 3rd-party integration. |
47
-
| IAM.Vendor.email | String | The employee's email address. |
48
-
| IAM.Vendor.errorCode | Number | HTTP error response code. |
49
-
| IAM.Vendor.errorMessage | String | Reason why the API failed. |
50
-
| IAM.Vendor.id | String | The employee's user ID in the app. |
51
-
| IAM.Vendor.instanceName | string | Name of the integration instance. |
52
-
| IAM.Vendor.success | Boolean | When true, indicates that the command was executed successfully. |
53
-
| IAM.Vendor.username | String | The employee's username in the app. |
54
-
45
+
| IAM.Vendor.active | Boolean | When true, indicates that the employee's status is active in the 3rd-party integration. |
46
+
| IAM.Vendor.brand | String | Name of the integration. |
47
+
| IAM.Vendor.details | string | Provides the raw data from the 3rd-party integration. |
48
+
| IAM.Vendor.email | String | The employee's email address. |
49
+
| IAM.Vendor.errorCode | Number | HTTP error response code. |
50
+
| IAM.Vendor.errorMessage | String | Reason why the API failed. |
51
+
| IAM.Vendor.id | String | The employee's user ID in the app. |
52
+
| IAM.Vendor.instanceName | string | Name of the integration instance. |
53
+
| IAM.Vendor.success | Boolean | When true, indicates that the command was executed successfully. |
54
+
| IAM.Vendor.username | String | The employee's username in the app. |
Updates an existing user with the data passed in the user-profile argument.
66
66
67
-
68
67
#### Base Command
69
68
70
69
`iam-update-user`
70
+
71
71
#### Input
72
72
73
73
|**Argument Name**|**Description**|**Required**|
74
74
| --- | --- | --- |
75
-
| user-profile | A User Profile indicator. | Required |
76
-
| allow-enable | When set to true, after the command execution the status of the user in the 3rd-party integration will be active. Possible values are: true, false. Default is true. | Optional |
77
-
75
+
| user-profile | A User Profile indicator. | Required |
76
+
| allow-enable | When set to true, after the command execution the status of the user in the 3rd-party integration will be active. Possible values are: true, false. Default is true. | Optional |
78
77
79
78
#### Context Output
80
79
81
80
|**Path**|**Type**|**Description**|
82
81
| --- | --- | --- |
83
-
| IAM.Vendor.active | Boolean | When true, indicates that the employee's status is active in the 3rd-party integration. |
84
-
| IAM.Vendor.brand | String | Name of the integration. |
85
-
| IAM.Vendor.details | string | Provides the raw data from the 3rd-party integration. |
86
-
| IAM.Vendor.email | String | The employee's email address. |
87
-
| IAM.Vendor.errorCode | Number | HTTP error response code. |
88
-
| IAM.Vendor.errorMessage | String | Reason why the API failed. |
89
-
| IAM.Vendor.id | String | The employee's user ID in the app. |
90
-
| IAM.Vendor.instanceName | string | Name of the integration instance. |
91
-
| IAM.Vendor.success | Boolean | When true, indicates that the command was executed successfully. |
92
-
| IAM.Vendor.username | String | The employee's username in the app. |
93
-
82
+
| IAM.Vendor.active | Boolean | When true, indicates that the employee's status is active in the 3rd-party integration. |
83
+
| IAM.Vendor.brand | String | Name of the integration. |
84
+
| IAM.Vendor.details | string | Provides the raw data from the 3rd-party integration. |
85
+
| IAM.Vendor.email | String | The employee's email address. |
86
+
| IAM.Vendor.errorCode | Number | HTTP error response code. |
87
+
| IAM.Vendor.errorMessage | String | Reason why the API failed. |
88
+
| IAM.Vendor.id | String | The employee's user ID in the app. |
89
+
| IAM.Vendor.instanceName | string | Name of the integration instance. |
90
+
| IAM.Vendor.success | Boolean | When true, indicates that the command was executed successfully. |
91
+
| IAM.Vendor.username | String | The employee's username in the app. |
0 commit comments