[llvm-dev] Question

[Andrew Santosa via llvm-dev]

Dear Samaneh,


You can probably use an alias analysis to compute stores that are tainted by input.

The following simple example shows the use of LLVM alias analysis. The example shows an implementation an intraprocedural analysis to detect the violation of rule STR30-C of the SEI-CERT C Coding Standard. 


https://gitlab.com/NUS-CS4239/llvm-assignments-examples/blob/master/lib/Analysis/StringLiteralWrite/StringLiteralWrite.cpp

You may need to modify the code to suit your purpose.

The description of STR30-C itself is here:

https://www.securecoding.cert.org/confluence/display/c/STR30-C.+Do+not+attempt+to+modify+string+literals

Best,
Andrew
On Thursday, 25 May 2017, 21:13, via llvm-dev <llvm-dev at lists.llvm.org> wrote:


Message: 10

Date: Thu, 25 May 2017 17:30:29 +0430

From: Samaneh Berenjian via llvm-dev <llvm-dev at lists.llvm.org>

To: llvm-dev at lists.llvm.org

Subject: [llvm-dev] Question

Message-ID: <1495717229938550848 at aut.ac.ir>

Content-Type: text/plain; charset="utf-8"


​Hi all,

I want to write some codes in form of IR for taint propagation. Does anyone have any idea or sample code for that?

Thank you in AdvanceBest regards

-- 

This email was Anti Virus checked by  Security Gateway.

-------------- next part --------------

An HTML attachment was scrubbed...

URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170525/c2e1f231/attachment-0001.html>


------------------------------


Subject: Digest Footer


_______________________________________________

llvm-dev mailing list

llvm-dev at lists.llvm.org

http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev



------------------------------


End of llvm-dev Digest, Vol 155, Issue 93

*****************************************