CVE-2023-41057: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in hyper-bump-it
First published: Mon Sep 04 2023(Updated: )
### Summary `hyper-bump-it` reads a file glob pattern from the configuration file. That is combined with the project root directory to construct a full glob pattern that is used to find files that should be edited. These matched files should be contained within the project root directory, but that is not checked. This could result in changes being written to files outside of the project. The default behaviour of `hyper-bump-it` is to display the planned changes and prompt the user for confirmation before editing any files. However, the configuration file provides a field that can be used cause files to be edited without displaying the prompt. ### Details The vulnerability is present in https://github.com/plannigan/hyper-bump-it/blob/49c726201bbdc02c052302e03fd907d2170e1f47/hyper_bump_it/_hyper_bump_it/files.py#L35 That code joins the project root directory with a string read from the configuration file without checking if the final path is located outside the project root directory. The following configuration file contents would cause `hyper-bump-it` to replace every instance of "hello" in every file adjacent to the project root directory with "world". The line setting `show_confirm_prompt` to `false` is not required, but will result in the user file edits to occur without the user having a chance to reject the changes (The fact that changes happened would still be displayed). ```toml [hyper-bump-it] current_version = "1.2.3" show_confirm_prompt=false [[hyper-bump-it.files]] file_glob = "../*" search_format_pattern = "hello" replace_format_pattern = "world" ``` ### Patches A fix that been released as part of v0.5.1. The changes can be view as part of PR #307. ### Workarounds Users that are unable to update from vulnerable versions, executing `hyper-bump-it` with the `--interactive` command line argument will ensure that all planned changes are displayed and prompt the user for confirmation before editing any files, even if the configuration file contains `show_confirm_prompt=true`.
Credit: security-advisories@github.com security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| pip/hyper-bump-it | <0.5.1 | 0.5.1 |
| Oracle Hyperion Planning | <0.5.1 |
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 the severity of CVE-2023-41057?
The severity of CVE-2023-41057 is classified as moderate.
How do I fix CVE-2023-41057?
To fix CVE-2023-41057, upgrade the 'hyper-bump-it' package to version 0.5.2 or higher.
What software is affected by CVE-2023-41057?
CVE-2023-41057 affects the 'hyper-bump-it' package version up to 0.5.1.
What is the nature of the vulnerability in CVE-2023-41057?
CVE-2023-41057 allows arbitrary file access through unvalidated file glob patterns.
Is CVE-2023-41057 exploitable in production environments?
Yes, CVE-2023-41057 can be exploited in production environments if the vulnerable software is in use.
- collector/github-advisory-latest
- alias/GHSA-xc27-f9q3-4448
- alias/CVE-2023-41057
- collector/github-advisory
- agent/references
- agent/type
- agent/remedy
- agent/softwarecombine
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/title
- agent/weakness
- agent/author
- agent/event
- agent/description
- agent/trending
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-cve
- collector/nvd-api
- package-manager/pip
- vendor/plannigan
- canonical/oracle hyperion planning