-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Defined Networking API Tokens Detector #1096
Conversation
Hi, I’m Jit, a friendly security platform designed to help developers build secure applications from day zero with an MVS (Minimal viable security) mindset. In case there are security findings, they will be communicated to you as a comment inside the PR. Hope you’ll enjoy using Jit. Questions? Comments? Want to learn more? Get in touch with us. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❌ Jit has detected 1 important finding in this PR that you should review.
The finding is detailed below as a comment.
It’s highly recommended that you fix this security issue before merge.
c6f4c23
to
67c7666
Compare
Rebased w/o the fixture to avoid setting off the detector xD |
Anything I can do to push this PR forwards? Sorry to ping, just wanted to know if this is the right place to contribute. |
@jasikpark would you mind rebasing? Global allowlists have been updated |
Adds detection support for Defined Networking tokens (https://docs.defined.net/guides/automating-host-creation/) I added a fixture in addition to the generator, I think I may be able to use the `generateUniqueToken` instead of the semi-generic option? Let me know if I should update accordingly. Remove testing fixture
67c7666
to
e201e87
Compare
@zricethezav done! |
woot 🥳 |
Description:
Adds detection support for Defined Networking tokens (https://docs.defined.net/guides/automating-host-creation/)
I added a fixture in addition to the generator, I think I may be able to use the
generateUniqueToken
instead of the semi-generic option? Let me know if I should update accordingly.Checklist: