GSA / GSA/ai-experience-sharing-platform
Finding: Insecure HTTP Method –PUT
- Dominant language
- JavaScript
- Stars
- 12
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
> This method was originally intended for file managemant operations. It is now most commonly used in REST services, PUT is most-often utilized for update capabilities, PUT-ing to a known resource URI with the request body containing the newly-updated representation of the original resource.
> Recommendation: Disable insecure methods such as DELETE, TRACK, TRACE, and CONNECT on the web server, and ensure that the underlying service implementation does not support insecure methods.
This finding involves considering if the PUT usage in Strapi is safe, and remediating if not (like #340).
Contributor guide
Research direction
Start by reviewing how Strapi handles PUT requests and compare the finding with issue #340. Determine whether the PUT usage is safe and identify the required remediation; done means the insecure-method finding is resolved or its safe use is documented with verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100