hohn/codeql
1
0
Fork 0
mirror of https://github.com/github/codeql.git synced 2025-12-16 16:53:25 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
0508d4fa33f289d1c6e49d05e927b3df2008f76f
codeql/python/old-change-notes/2021-02-10-django-improvements.md
Dave Bartolomeo fa40d59332 Move older change notes to old-change-notes 
Now that change notes are per-package, new change notes should be created in the `change-notes` folder under the affected pack (e.g., `cpp/ql/src/change-notes` for C++ query change notes. I've moved all of the change note files that were added before we started publishing them in packs to an `old-change-notes` directory under each language, to reduce the temptation to add new change notes there.

I'm working on a document to describe how and when to create change notes for packs separately.
2021-12-14 12:35:04 -05:00

785 B
Raw Blame History

lgtm,codescanning

  • Improved modeling of django to recognize request handlers functions that are decorated (for example with django.views.decorators.http.require_GET). This leads to more sources of remote user input (RemoteFlowSource), since we correctly identify the first parameter as being passed a django request.
  • Improved modeling of django View classes. We now consider any class using in a routing setup with <class>.as_view() as django view class. This leads to more sources of remote user input (RemoteFlowSource), since we correctly identify the first parameter as being passed a django request.
  • Improved modeling of django, so for View classes we now model self.request, self.args, and self.kwargs as sources of remote user input (RemoteFlowSource).