Skip to content

Conversation

@akath20
Copy link
Contributor

@akath20 akath20 commented Mar 28, 2020

SWEN 331 Research Work for CVE-2014-0472 (Django) and CVE-2016-9013 (Django)

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
Copy link
Contributor

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
Copy link
Contributor

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: |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

upvotes: 1

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

upvotes: 1

@andymeneely andymeneely merged commit 02612a3 into VulnerabilityHistoryProject:dev Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants