fix: multiple api endpoints across flight-esm and fl... in region.js#36164
fix: multiple api endpoints across flight-esm and fl... in region.js#36164orbisai0security wants to merge 1 commit intofacebook:mainfrom
Conversation
Multiple API endpoints across flight-esm and flight fixtures expose functionality without any authentication mechanisms
|
Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Summary
Fix critical severity security issue in
fixtures/flight-esm/server/region.js.Vulnerability
V-001fixtures/flight-esm/server/region.js:44Description: Multiple API endpoints across flight-esm and flight fixtures expose functionality without any authentication mechanisms. The endpoints GET /, POST /, GET /todos, and GET /source-maps can be accesse...
Changes
fixtures/flight-esm/server/region.jsVerification
Automated security fix by OrbisAI Security