GHSA-hwv5-w8gm-fq9f

Suggest an improvement
Source
https://github.com/advisories/GHSA-hwv5-w8gm-fq9f
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2020/10/GHSA-hwv5-w8gm-fq9f/GHSA-hwv5-w8gm-fq9f.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-hwv5-w8gm-fq9f
Aliases
Published
2020-10-06T18:21:02Z
Modified
2024-11-19T18:25:41.611627Z
Severity
  • 3.5 (Low) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N CVSS Calculator
  • 2.3 (Low) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N CVSS Calculator
Summary
Directory Traversal vulnerability in GET/PUT allows attackers to Disclose Information or Write Files via a crafted GET/PUT request
Details

Impact

Information Disclosure

When the GET method is attacked, attackers can read files which have a .data suffix and which are accompanied by a JSON file with the .meta suffix. This can lead to Information Disclosure and in some shared-hosting scenarios also to circumvention of authentication or other limitations on the outbound (GET) traffic.

For example, in a scenario where a single server has multiple instances of the application running (with separate DATA_ROOT settings), an attacker who has knowledge about the directory structure is able to read files from any other instance to which the process has read access.

If instances have individual authentication (for example, HTTP authentication via a reverse proxy, source IP based filtering) or other restrictions (such as quotas), attackers may circumvent those limits in such a scenario by using the Directory Traversal to retrieve data from the other instances.

File Write

If the associated XMPP server (or anyone knowing the SECRETKEY) is malicious, they can write files outside the DATAROOT. The files which are written are constrained to have the .meta and the .data suffixes; the .meta file will contain the JSON with the Content-Type of the original request and the .data file will contain the payload.

Patches

PR #12 fixes the issue. The PR has been merged into version 0.4.0 and 0.4.0 has been released and pushed to PyPI. Users are advised to upgrade immediately.

Workarounds

  • Apache can apparently be configured to filter such malicious paths when reverse-proxying.
  • There are no other workarounds known.

References

Database specific
{
    "nvd_published_at": null,
    "cwe_ids": [
        "CWE-22"
    ],
    "severity": "LOW",
    "github_reviewed": true,
    "github_reviewed_at": "2020-10-06T18:20:50Z"
}
References

Affected packages

PyPI / xmpp-http-upload

Package

Name
xmpp-http-upload
View open source insights on deps.dev
Purl
pkg:pypi/xmpp-http-upload

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.4.0

Affected versions

0.*

0.1
0.2.0
0.3.0