ProjectSend Improper Authentication
CVE-2024-11680 is a critical-severity missing authentication for critical functionality vulnerability in ProjectSend, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version r1720 as the first without the flaw, so updating ProjectSend to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on December 3, 2024, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update ProjectSend to r1720 or a later version.
- CISA's required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| ProjectSend | ProjectSend | before r1720 | r1720 |
Version data comes from the organisation that assigned the CVE. 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
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- 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:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | CNA (vulncheck.com) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Remote, unauthenticated attackers can exploit this flaw by sending crafted HTTP requests to options.php, enabling unauthorized modification of the application's configuration. Successful exploitation allows attackers to create accounts, upload webshells, and embed malicious JavaScript.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authentication for Critical Functionality
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.
More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)
Timeline
- CVE record published.
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- CISA published its SSVC assessment (exploitation: active, automatable: yes, technical impact: total).
- Deadline for US federal agencies to remediate, set by CISA.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/projectsend/projectsend/commit/193367d937b1a59ed5b68dd4e60bd53317473744
- synacktiv.com/sites/default/files/2024-07/synacktiv-projectsend-multiple-vulnerabilities.pdfMitigation, Technical Description, Third Party Advisory
Third-party and government advisories
- vulncheck.com/advisories/projectsend-bypassThird Party Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-11680US Government Resource
Technical write-ups (may include proof of concept)
Other vulnerabilities in ProjectSend
- 7.2 High severity
- 9.8 Critical severity
- 7.5 High severity
- 8.0 High severity
- 7.5 High severity
Recent Missing Authentication for Critical Functionality vulnerabilities
- 9.8 Critical severity
- 8.1 High severity
- 8.1 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 8.8 High severity
Spotted an error? Tell us.