GHSA-gqcf-83rq-gpfr: Ibexa/post install Any Storage File Can Be Vulnerability

HIGH
CWE-200
Published
Advisory Summary

GHSA-gqcf-83rq-gpfr is a HIGH any storage file can be vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Ibexa/post install libraries in the Packagist ecosystem. The issue involves any storage file can be downloaded from p.sh if full server path is known. Remediation is available by upgrading affected packages to version 1.0.4.1.

GHSA-gqcf-83rq-gpfr at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-gqcf-83rq-gpfr
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Ibexa/post install
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix GHSA-gqcf-83rq-gpfr

To remediate this vulnerability, upgrade all affected Ibexa/post install dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

ibexa/post-install fixed: 1.0.4.1
Upgrade ibexa/post-install to 1.0.4.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for ibexa/post-install

How to Check if You Are Affected

To determine whether your application is affected by GHSA-gqcf-83rq-gpfr, inspect your project dependencies for Ibexa/post install:

inspect dependencies for ibexa/post-install

Analyze the terminal output to locate any version of Ibexa/post install in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.0.4.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Ibexa/post install, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

The default configuration for platform.sh (.platform.app.yaml) allows access to uploaded files if you know or can guess their location, regardless of whether roles grant content read access to the content containing those files. If you're using Legacy Bridge, the default configuration also allows access to certain legacy files that should not be readable, including the legacy var directory and extension directories.

GHSA-gqcf-83rq-gpfr Affected Ibexa/post install Versions

1 component(s)
Fixed Versions:
1.0.4.1
Product / Package Ecosystem Affected Versions Fixed Version
ibexa/post-install
Packagist
< 1.0.4.1
1.0.4.1

References

Frequently Asked Questions

What is GHSA-gqcf-83rq-gpfr?
GHSA-gqcf-83rq-gpfr is a security vulnerability in Ibexa/post install involving Any storage file can be downloaded from p.sh if full server path is known under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Ibexa/post install versions are affected?
Affected versions include releases prior to 1.0.4.1 across affected packages: ibexa/post-install.
What version fixes GHSA-gqcf-83rq-gpfr?
Upgrading to 1.0.4.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is ibexa/post-install affected?
Yes, ibexa/post-install is affected in releases prior to 1.0.4.1. Upgrade your dependency to 1.0.4.1 or later.
What CWE is associated with GHSA-gqcf-83rq-gpfr?
GHSA-gqcf-83rq-gpfr is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check Packagist dependencies for GHSA-gqcf-83rq-gpfr?
Run the dependency tree command: 'inspect dependencies for ibexa/post-install'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-gqcf-83rq-gpfr",
  "modified" : "2021-09-14T18:35:35Z",
  "published" : "2021-09-14T20:24:44Z",
  "aliases" : [ ],
  "summary" : "Any storage file can be downloaded from p.sh if full server path is known",
  "details" : "The default configuration for platform.sh (.platform.app.yaml) allows access to uploaded files if you know or can guess their location, regardless of whether roles grant content read access to the content containing those files. If you're using Legacy Bridge, the default configuration also allows access to certain legacy files that should not be readable, including the legacy var directory and extension directories.",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "ibexa/post-install"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.0.4.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.0.4"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/ibexa/post-install/security/advisories/GHSA-gqcf-83rq-gpfr"
  }, {
    "type" : "WEB",
    "url" : "https://developers.ibexa.co/security-advisories/ibexa-sa-2021-006-storage-and-legacy-files-accessible-if-path-is-known"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/ibexa/post-install"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-09-14T18:35:35Z",
    "nvd_published_at" : null
  }
}