CVE-2020-15239

In xmpp-http-upload before version 0.4.0, 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. If the associated XMPP server (or anyone knowing the SECRET_KEY) is malicious, they can write files outside the DATA_ROOT. 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. The issue is patched in version 0.4.0.

• CVE ID
• CVE-2020-15239

• Assigner
• security-advisories@github.com

• Vulnerability Status
• Analyzed

• Published Version
• 2020-10-06T19:15:13

• Last Modified Date
• 2020-10-23T03:09:55

• Version
• 2.0

• Vector String
• AV:N/AC:L/Au:S/C:P/I:N/A:N

• Access Vector
• NETWORK

• Access Compatibility
• LOW

• Authentication
• SINGLE

• Confidentiality Impact
• PARTIAL

• Integrity Impact
• NONE

• Availability Impact
• NONE

• Base Score
• 4

• Severity
• MEDIUM

• Exploitability Score
• 8

• Impact Score
• 2.9

• Version
• 3.1

• Vector String
• CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N

• Attack Vector
• NETWORK

• Attack Compatibility
• HIGH

• Privileges Required
• LOW

• User Interaction
• NONE

• Scope
• CHANGED

• Confidentiality Impact
• LOW

• Availability Impact
• NONE

• Base Score
• 3.5

• Base Severity
• LOW

• Exploitability Score
• 1.8

• Impact Score
• 1.4