-
Notifications
You must be signed in to change notification settings - Fork 51
CVE-2014-0472 and CVE-2016-9013 #5
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
Conversation
cves/CVE-2014-0472.yml
Outdated
| This VCC was discovered automatically via archeogit. This was where | ||
| I originally thought the problem was introduced, but this was a refactor | ||
| of moving where the function lived. | ||
| - commit: 5d568bcfa66916e3de61e0090c724c899debd981 |
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.
If a commit that was discovered isn't relevant or isn't the specific part in the code that where the VCC is introduced then it should be removed!
| developer to get the tests running. However, the lesson to be learned here | ||
| would be when you're adding a new feature, especially a security based on, | ||
| look through the exisiting features of that component and how the new | ||
| feature would mesh and/or create unforessen complications with exisiting |
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.
Just in general for all your answers, I would stray away from using first person perspective.
| feature patch to bring in multiple database support including Oracle | ||
| database which did include refactoring and moving around | ||
| the password that was used/created in the test database. | ||
| upvotes_instructions: | |
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.
upvotes: 1
cves/CVE-2014-0472.yml
Outdated
| This VCC was discovered automatically via archeogit. This was where | ||
| I originally thought the problem was introduced, but this was a refactor | ||
| of moving where the function lived. | ||
| - commit: 5d568bcfa66916e3de61e0090c724c899debd981 |
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.
upvotes: 1
SWEN 331 Research Work for CVE-2014-0472 (Django) and CVE-2016-9013 (Django)