Conversation
- Introduced Challenge 73, which focuses on identifying a leaked secret in agent instruction files included in the dev container. - Updated Dockerfile to copy new agent context files into the container. - Added documentation for the challenge in AGENTS.md, CLAUDE.md, and new explanation files. - Updated README to reflect the total number of challenges. - Implemented tests to validate the challenge functionality and ensure correct token extraction from context files.
Collaborator
|
Hi @kekubhai , thank you for another awesome PR! Spot bugs breaks, saying: in https://github.com/OWASP/wrongsecrets/actions/runs/35695091564/job/106640110735?pr=2687 Can you fix that please :) ? |
Contributor
Author
sure i will look inito these and work on fixing these |
…swer() SpotBugs 4.10.4 no longer flags the method since the file names come from a fixed constant list, so the annotation triggered US_USELESS_SUPPRESSION_ON_METHOD. 🤖 Generated with Codebuff Co-Authored-By: Codebuff <[email protected]>
…into feat/2656-agent-config-secrets
…AT_STRING_USES_NEWLINE 🤖 Generated with Codebuff Co-Authored-By: Codebuff <[email protected]>
…ekubhai/wrongsecrets-keku into feat/2656-agent-config-secrets
…ions The config pointed at k8s.llama.Challenge74 but the class lives in kubernetes.llama, so findChallenge() returned empty and submitting an answer on the challenge page threw ChallengeConfigurationException, failing the Cypress incorrect-alert e2e test. 🤖 Generated with Codebuff Co-Authored-By: Codebuff <[email protected]>
…ekubhai/wrongsecrets-keku into feat/2656-agent-config-secrets
Contributor
Author
|
hey @commjoen resolved the CI failures and the bugs I had , have a look pls |
Collaborator
|
Hi @kekubhai ! It is looking awesome already. I Will take a better look next week, can you resolve the conflicts in the meantime please? |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of changes does this PR include?
Description
Introduces Challenge 73, focused on secrets accidentally exposed through AI coding-agent instruction and context files shipped with the dev container.
The challenge adds common agent configuration files:
AGENTS.mdCLAUDE.md.cursor/rules/project.mdc.windsurfrulesOne of these files contains a leaked staging deployment token that participants must discover.
The implementation:
FixedAnswerChallengepattern.wrong-secrets-configuration.yaml.Relations
Closes #2656
References
The challenge follows the existing AI-related challenge patterns and uses agent instruction/context files as the intentionally insecure location for the secret.
Checklist: