Paymoney: Unrestricted Upload of File with Dangerous Type
CVE-2022-37140 is a high-severity unrestricted upload of file with dangerous type vulnerability in Paymoney from Techvill, with a CVSS 3.1 base score of 8.0 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, but only if a user takes part, for example by opening a link or file. Affected Paymoney versions: 3.3. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.79% chance of exploitation within 30 days, higher than 79% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Paymoney you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on paymoney.techvill.org for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.
Official description
PayMoney 3.3 is vulnerable to Client Side Remote Code Execution (RCE). The vulnerability exists on the reply ticket function and upload the malicious file. A calculator will open when the victim who download the file open the RTF file.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Unrestricted Upload of File with Dangerous Type
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
How developers prevent this class of flaw
- Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
- When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
- Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically.
More Unrestricted Upload of File with Dangerous Type vulnerabilities (CWE-434)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
Technical write-ups (may include proof of concept)
- github.com/saitamang/POC-DUMP/tree/main/PayMoneyExploit, Third Party Advisory
Recent Unrestricted Upload of File with Dangerous Type vulnerabilities
- 8.8 High severity
- 8.8 High severity
- 9.8 Critical severity
- 7.2 High severity
- 7.2 High severity
- 8.8 High severity
Spotted an error? Tell us.