Improper neutralization of CRLF sequences in GitHub Enterprise Server allowed branch protection bypass via pull request conflict resolution
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.
No data available yet.
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 |
|---|---|---|
| Description | A CRLF injection vulnerability was identified in GitHub Enterprise Server that allowed a user with write access to a repository to bypass branch protections and update branches or tags in that repository through specially crafted input when resolving pull request conflicts. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.23 and was fixed in versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5. This vulnerability was reported via the GitHub Bug Bounty program. | |
| Title | Improper neutralization of CRLF sequences in GitHub Enterprise Server allowed branch protection bypass via pull request conflict resolution | |
| Weaknesses | CWE-93 | |
| References |
|
|
| Metrics |
cvssV4_0
|
No data.
Improper Neutralization of CRLF Sequences ('CRLF Injection')