CVE-2022-46258
First published: Mon Jan 09 2023(Updated: )
An incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed a repository-scoped token with read/write access to modify Action Workflow files without a Workflow scope. The Create or Update file contents API should enforce workflow scope. This vulnerability affected all versions of GitHub Enterprise Server prior to version 3.7 and was fixed in versions 3.3.16, 3.4.11, 3.5.8, and 3.6.4. This vulnerability was reported via the GitHub Bug Bounty program.
Credit: product-cna@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitHub Enterprise Server | <3.3.16 | |
| GitHub Enterprise Server | >=3.4.0<3.4.11 | |
| GitHub Enterprise Server | >=3.5.0<3.5.8 | |
| GitHub Enterprise Server | >=3.6.0<3.6.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2022-46258?
CVE-2022-46258 is an incorrect authorization vulnerability in GitHub Enterprise Server.
What is the severity of CVE-2022-46258?
The severity of CVE-2022-46258 is medium with a CVSS score of 6.5.
How does CVE-2022-46258 affect GitHub Enterprise Server?
CVE-2022-46258 affects GitHub Enterprise Server versions up to 3.3.16, 3.4.0 to 3.4.11, 3.5.0 to 3.5.8, and 3.6.0 to 3.6.4.
How can I fix CVE-2022-46258?
To fix CVE-2022-46258, update GitHub Enterprise Server to a version that is not affected by the vulnerability.
Where can I find more information about CVE-2022-46258?
More information about CVE-2022-46258 can be found in the GitHub Enterprise Server release notes.
- collector/nvd-index
- vendor/github
- product/enterprise server
- canonical/github enterprise server