Repository destruction via unchecked release-directory root
Published Sep 22, 2023 · Updated Sep 24, 2024
Improper input validation in AutomataCI 1.4.1 and earlier allows local users to erase repository history through a release job. The GIT::hard_reset_to_init function fails to verify that PROJECT_PATH_RELEASE is a separate Git repository before hard-resetting it to its initial commit and force-pushing it. Triggering the release job with a missing or malformed release directory causes destructive changes to the root repository and its remote, and user interaction is required.
Summary
What happened
Improper input validation in AutomataCI 1.4.1 and earlier allows local users to erase repository history through a release job. The GIT::hard_reset_to_init function fails to verify that PROJECT_PATH_RELEASE is a separate Git repository before hard-resetting it to its initial commit and force-pushing it. Triggering the release job with a missing or malformed release directory causes destructive changes to the root repository and its remote, and user interaction is required.
The record
- CVE
- CVE-2023-42798
- Published
- Sep 22, 2023
- Updated
- Sep 24, 2024
- Vendor
- Chew, Kean Ho
- Product
- AutomataCI
- Classifications
- CWE-20, T1485
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 22, 2023CVE publishedPublication date reported by the CVE source.
- Sep 24, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo