Added specificity to the prompt to stop LLM to assume a package and function within a code base is being used to create an image #53
Conversation
This file contains 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
…unction within a code base to crreating an image
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The initial checklist prompt for checklist made the LLM hallucinate and assume that imagebuilder and builder package is being used to create the container image which is untrue. Please refer section 1.1 of Tool Output from here - https://github.com/mpaulgreen/vul_results/blob/main/CVE-2024-0406.md
We should prevent LLM to assume that any part of the code base is been used to create that image. Here is the output after changing the prompt.
https://github.com/mpaulgreen/vul_results/blob/main/CVE-2024-0406_revised.md
Let me know your thoughts. If you all agree then we can apply these modifications downstream.