Security readout for executives and security teams
Plain-English summary
A malicious devfile can cause registry-support to download and unpack an archive whose cleanup reaches outside its intended directory. If a user processes that devfile, unrelated files may be overwritten or deleted, potentially disrupting development or OpenShift operations. Interaction is required, but the devfile can originate from an unauthenticated remote attacker.
Executive priority
Prioritize near-term remediation for systems processing externally sourced devfiles, especially automated or privileged workflows. The potential impact is file destruction or overwrite rather than data theft. Where devfiles are trusted and processing runs with limited permissions, urgency is lower, but version status should still be confirmed promptly.
Technical view
CVE-2024-1485 is a CWE-22 path traversal flaw in registry-support decompression cleanup. A crafted archive referenced through devfile parent or plugin keywords may use relative paths to escape the archive scope. The stated impact is high-integrity and availability loss without confidentiality impact. CVSS 3.1 is 8.0, with network reachability, high complexity, user interaction, and changed scope.
Likely exposure
Exposure exists where users or automation parse untrusted devfiles using affected registry-support functionality. The bundle identifies odo and OpenShift Container Platform 4 ose-console as affected, but supplies no affected version ranges. Its registry-support 1.16.2 status is marked unaffected, creating version ambiguity that requires vendor confirmation.
Exploitation context
Exploitation requires a victim or workflow to parse an attacker-influenced devfile containing parent or plugin references. Those references can retrieve a malicious archive, after which cleanup may alter files outside its directory. The CVE is not listed in KEV, and the supplied sources provide no evidence of active exploitation.
Researcher notes
The source bundle links an upstream commit and pull request, indicating a code-level correction exists, but it does not name a fixed release. Affected-version data is incomplete and internally ambiguous: registry-support 1.16.2 is listed with defaultStatus unaffected, while Red Hat products lack ranges. Validate boundaries against current vendor advisories before declaring exposure.
Mitigation direction
- Review Red Hat and upstream guidance for corrected, supported releases.
- Update affected odo, OpenShift, or registry-support components according to vendor guidance.
- Restrict processing of devfiles from untrusted or unverified sources.
- Limit filesystem permissions of services and users that process devfiles.
- Review automation accepting externally supplied devfiles or registry content.
Validation and detection
- Inventory registry-support, odo, and OpenShift ose-console deployments and versions.
- Compare installed versions with current Red Hat and upstream advisories.
- Identify workflows that process devfile parent or plugin references.
- Review relevant logs and filesystem changes for unexpected deletions or overwrites.
- Confirm remediation using benign regression tests for archive path containment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-1485 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:H1.65.8redhatVulnerability scoring details
Base CVSS 3.1 score
8HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Made public.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://access.redhat.com/security/cve/CVE-2024-1485CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2264106CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://github.com/advisories/GHSA-84xv-jfrm-h4gmCVE reference, redhat
- https://github.com/devfile/registry-support/commit/0e44b9ca6d03fac4fc3f77d37656d56dc5defe0dCVE reference, redhat
- https://github.com/devfile/registry-support/pull/197CVE reference, redhat
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.