Builder crash via untrimmed RUN trailing spaces
Published Jul 26, 2021 · Updated Aug 3, 2024
Denial of service in openEuler isula-build before 0.9.5-6 allows remote attackers to crash isula-builder via a crafted Dockerfile. The Dockerfile RUN-instruction path leaves multiple trailing spaces in externally supplied build data instead of trimming them, and the malformed input triggers a panic. Reachability requires submission of a container-image build containing the crafted RUN line; the bounded consequence is interruption of the builder process.
Summary
What happened
Denial of service in openEuler isula-build before 0.9.5-6 allows remote attackers to crash isula-builder via a crafted Dockerfile. The Dockerfile RUN-instruction path leaves multiple trailing spaces in externally supplied build data instead of trimming them, and the malformed input triggers a panic. Reachability requires submission of a container-image build containing the crafted RUN line; the bounded consequence is interruption of the builder process.
The record
- CVE
- CVE-2021-33629
- Published
- Jul 26, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
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