Economy Cybersecurity
ProjectSend fixes a flaw in public links found by Webcracy
Liam Giannini of Webcracy found that a ProjectSend client could read and revoke public links created by staff on the client's own files, even without permission to publish such links. The flaw, of moderate severity, is fixed in version 2.8.0.
Webcracy, the Locarno-based cybersecurity firm, reported a vulnerability in ProjectSend, an open source application that professional firms and companies use to manage and share files with their clients through a web portal. It was discovered by Liam Giannini, the company's co-founder and an ethical hacker. The issue, catalogued as GHSA-g9g5-qxp7-f7v2 and published on November 8, is fixed in version 2.8.0.
On the portal, the client uploads documents; staff review them and, when needed, generate a public address to send to third parties, usable without the recipient having to log into the system. Creating these addresses requires a specific permission, called upload_public, which the administrator grants or denies to each role. As for who can see them, the program already had a clear rule in place: the file list in the client portal shows only the addresses generated by that same client, not the ones staff generate on the same file to send it elsewhere, for instance to an outside consultant.
Two places where the rule did not apply
That rule was not applied everywhere. When opening the edit page for one of their own files, a client with permission to edit it could see, in full, every public link tied to that file, including those created by staff, complete with the full address and access code. Deletion had the same flaw: the system checked whether the client could edit the file, but not who had actually created that particular link. The result: a client denied publishing permission by the administrator could still circulate a link created by staff, or delete a link staff had shared with an outside party, cutting off access that someone else had decided to grant.
The issue only affects files uploaded by the client themselves, and requires staff to have created a public link on top of it: it grants no access to other clients' files and no extra privileges. The advisory rates it as moderate severity, under CWE-862 and CWE-200, with an estimated CVSS of 5.4. Versions 2.5.0 through 2.7.1 are affected.
To track the problem down, Giannini compared the three paths through which the application reaches the same link: the portal list, the file editor, and the revocation function. Only the first applied the filter by author. To confirm it, he wrote four automated tests, run in an isolated container with fake data and accounts, alongside two control tests already present in the project.
The release notes for 2.8.0, out on October 29, also fix other authorization issues in the same application: API tokens with broader rights than intended, compressed archives that remained downloadable after access to a file was revoked, and uploaded files that ended up in folders no longer meant to be accessible to the user. ProjectSend has been used by professional firms and companies since 2014 and has over 2,000 stars on GitHub; the Docker image distributed by LinuxServer.io alone has passed 4.9 million downloads.
Anyone running a version between 2.5.0 and 2.7.1 should update to 2.8.0. After updating, it is worth reviewing the public links staff have created on client files: a link already shared with outside parties remains known to whoever received it, so it should be revoked and recreated if the client was never meant to see it. For these findings, Webcracy follows a responsible disclosure process already applied to other open source projects such as exarch and FreeScout: maintainers are informed privately, and the issue is only made public once it is fixed.
Comments
There are no comments yet. Yours can be the first voice.

