Server-side request forgery in GitHub Enterprise Server enabled remote code execution via Slack webhook validity checks
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| GitHub | Enterprise Server | unknown |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Github | Enterprise Server |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Github
Github enterprise Server |
|
| Vendors & Products |
Github
Github enterprise Server |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A server-side request forgery vulnerability in GitHub Enterprise Server allowed an authenticated user with repository write access to send requests to internal services through Slack webhook validity checks, potentially leading to remote code execution on the appliance. Exploitation required Secret Protection with secret scanning and validity checks for partner patterns enabled. This vulnerability affected all versions prior to 3.23 and was fixed in versions 3.22.5, 3.21.10, and 3.20.12. This vulnerability was reported via the GitHub Bug Bounty program. | |
| Title | Server-side request forgery in GitHub Enterprise Server enabled remote code execution via Slack webhook validity checks | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV4_0
|
No data.