Skip to content
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.

Sign up for GitHub

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

Jump to bottom

solution for challenge 1 is identical to the solution of challenge 2 #145

Closed
davevs opened this issue Jan 10, 2022 · 1 comment · Fixed by #146
Closed

solution for challenge 1 is identical to the solution of challenge 2 #145

davevs opened this issue Jan 10, 2022 · 1 comment · Fixed by #146

Comments

@davevs
Copy link

davevs commented Jan 10, 2022

de secret leaked in the .class of challenge 1 is the same as the secret in the application.properties in challenge 2.
Although not really a big problem since you have to solve the challenge to see it, I think it makes sense from a CTF perspective to make them different.
commjoen added a commit that referenced this issue Jan 10, 2022
@commjoen
Fix for #145 : changing the secret of challenge 2
f771b57
@commjoen commjoen mentioned this issue Jan 10, 2022
Merged
@davevs
Copy link
Author

davevs commented Jan 10, 2022

fixed

@davevs davevs closed this as completed Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix for #145 : changing the secret of challenge 2 OWASP/wrongsecrets
1 participant
@davevs