Skip to content
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

Create SECURITY.dc #3168

Open
wants to merge 3,317 commits into
base: cs/assembly-prefix
Choose a base branch
from
Open

Create SECURITY.dc #3168

wants to merge 3,317 commits into from

Conversation

wdcne
Copy link

@wdcne wdcne commented Mar 31, 2020

No description provided.

BekaValentine and others added 30 commits March 16, 2020 11:24
JS: loosen qldoc for `barrierGuardIsRelevant`
Co-Authored-By: Esben Sparre Andreasen <esbena@github.com>
Docs: refactor guidelines for new queries
This change introduces a new synthesized `IRVariable` in every varargs function. This variable represents the entire set of arguments passed to the ellipsis by the caller. We give it an opaque type big enough hold all of the arguments passed by the largest vararg call in the database. It is treated just like any other parameter. It is initialized the same, it has indirect buffers, etc.

I had to introduce a couple new APIs to `Call` and `Function`. The QLDoc comments should explain these. I added tests for these new APIs as well.

The next step will be to change the IR generation for the `va_*` macros to manipulate the ellipsis parameter.
RasmusWL and others added 28 commits March 27, 2020 16:20
Change 'Set Literals' to 'Set literals'
C++: Fix test expectations for complex literals
…roughFlowCand

Data flow: No magic in returnFlowCallableCand
…teps

Java: Add taint steps through Jackson serialization methods.
…cking-taint-CP

Python: Fix iterable-unpacking taint CP
Modelled after the correponding comment for `DataFlowImpl.qll`.
Data flow: Add module doc comment for `TaintTrackingImpl.qll`
…checks

Java: Add data-flow consistency checks.
How could the tests fail because of autoformatting, you may ask?

The answer is deprecation warnings. These specify the location of the deprecated
entity, and due to autoformatting these moved around.
This consistency check seems to have value for AST data flow, but I've
disabled it on the IR for now.

This commit also includes two unrelated changes that seem to fix a
semantic merge conflict.
…verything

Python: Autoformat (almost) all `.qll` files.
…iles

Python: Autoformat all `.ql` files.
rewrote the qldoc to explain it as well.
otherwise the helper predicate can (and sometimes will) be evaluated once _per_
instance of that class.
C++: Remove noise from argHasPostUpdate check
…zer-example

Python: Add example for how to write your own sanitizer
@ghost
Copy link

ghost commented Mar 31, 2020

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@wdcne wdcne changed the base branch from master to cs/assembly-prefix March 31, 2020 01:56
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.