News for hackers. Stuff that matters.
Re:Coverity Scan Update by walterbell on Wednesday January 09, 2019 @04:50PM (#18869295)
Has anyone tried LGTM / Semmle QL for automated code review? They claim 100K OSS projects are using the service. It's a bit hard to find technical information on the product, but they have found CVEs in mainstream products, including iOS.

https://lgtm.com & https://semmle.com/ql

Re:Coverity Scan Update by spatulon on Wednesday January 09, 2019 @05:40PM (#18869748)
I work on C/C++ analysis at Semmle, and am happy to answer any questions you might have. (We also support C#, Java, JavaScript, Python... and Cobol!)

We have a few high-profile projects using our automated code review (marketing people tell me I'm not allowed to call it 'PR integration' any more). One example is on the AMP Project, where we caught a regex injection vulnerability in a PR before a human looked at it: https://github.com/ampproject/amphtml/pull/13060

Our default analysis has found a few other vulnerabilities (remote buffer overflows due to misuse of snprintf in rsyslog and Icecast spring to mind) but, honestly, I think our strength lies in the fact that you can write custom queries that find bugs specific to a single codebase's foibles.

For example, my first ever CVE was for a vulnerability in ChakraCore. Google Project Zero found the original bug - type confusion caused by failure to check a flag indicating that the last element of a list should be cast to a different type - but we wrote a query to verify that code accessing that particular list always checked the flag. So when some new code got introduced with the same bug, we noticed as soon as we re-ran the query on the new commit.

Re:Coverity Scan Update by walterbell on Wednesday January 09, 2019 @06:49PM (#18870236)
Is there a public language reference on the query language? The Help section of the website only has intro examples. How long does it take for a new developer to learn to write non-trivial queries?

Any technical comparisons with other static analysis tools?

It would be useful to have a public database of QL sample queries alongside matching OSS code snippets. In theory, this could be constructed from Github, but presumably LGTM already has that historical viewpoint.

Re:Coverity Scan Update by spatulon on Wednesday January 09, 2019 @07:24PM (#18870436)
I think the QL handbook is what you're looking for: https://help.semmle.com/QL/ql-handbook/

Other QL references (such as the reference manuals for the language-specific libraries) are linked from here: https://help.semmle.com/QL/ql-home.html

Personally (having joined the company reasonably recently), I haven't found it particularly hard to figure out how to express my intentions in QL. Most complex queries start their lives as simple ones that return too many results; the complexity comes from adding extra conditions to refine the results, and is generally manageable. However, I do occasionally have difficulties where a query I'm developing returns no results, and my years of experience debugging imperative programs don't really help as much as I would like in figuring out what's wrong. It can also be quite easy for beginners to write queries that are interminably slow for non-obvious reasons; I believe we're working on documentation to help with that.

We do have a database of all the default queries here: https://help.semmle.com/wiki/display/QL/Built-in+queries

But I notice that not all of them have examples, and many of the examples we do have are fairly contrived. I like your idea of taking snippets from matching OSS projects.

Edit: our CEO gently reminded me that, if you look at the help page on lgtm.com for a particular query/rule/alert, you can get a list of all results across every OSS project we analyse, e.g. https://lgtm.com/rules/1506728586782/alerts/

Re:Coverity Scan Update by walterbell on Wednesday January 09, 2019 @09:36PM (#18871060)
Thanks for the references, that last link is very cool!

> It can also be quite easy for beginners to write queries that are interminably slow for non-obvious reasons; I believe we're working on documentation to help with that

RDBMS have the same challenge. Data visibility for query parser internals can help, https://www.embarcadero.com/images/dm/technical-papers/sybas...

Re:Coverity Scan Update by walterbell on Wednesday January 09, 2019 @10:46PM (#18871343)
> We also support C#, Java, JavaScript, Python... and Cobol!)

Where do these rank in chances of future support?

  - Go
  - Rust
  - Lua
  - Swift
  - Haskell
Re:Coverity Scan Update by samlanning on Thursday January 10, 2019 @06:27AM (#18873105)
Go support is currently in development, so very likely :)

As for the other languages there, there are no plans currently on the roadmap for 2019 to add any of them. However if this is something that particularly interests you, we'd encourage you to apply for a job and note that you'd like to add support for a particular language :)

Re:Coverity Scan Update by nestinos on Thursday January 10, 2019 @06:11AM (#18873032)
Re:Coverity Scan Update by rgerhards on Thursday January 10, 2019 @07:30AM (#18873365)
We at rsyslog use it as part of our CI pipeline. It's a pretty cool tool, done by awesome folks. A real big plus is the responsiveness to questions and when something needs attention. When we came to LGTM (at that time in beta for C), we already had a pretty clean code base. The reason is that we use other static analysis tools. LGTM did nevertheless find some new and interesting things, include a real vulnerability[1]. We don't use custom QL right now (time is soo short), but opt in to some extra canned queries. For example, we prevent commented-out code via them. LGTM is a check REQUIRED to pass CI [2, sample PR].

We are really happy with both the product and the team and I can recommend diving into it. Nevertheless, don't rely on a single static analysis tool, no matter how good it is. If you use C/C++, you should at least also have clang's static analyzer in use.

[1] https://rainer.gerhards.net/2018/06/how-we-found-and-fixed-c... [2] https://github.com/rsyslog/rsyslog/pull/3403

Re:Coverity Scan Update by samlanning on Wednesday January 09, 2019 @05:51PM (#18869834)
Systemd and tesseract-ocr both use it for example:

https://github.com/tesseract-ocr/tesseract https://github.com/systemd/systemd

systemd have also written their own QL query: https://github.com/systemd/systemd/blob/master/.lgtm/cpp-que... https://lgtm.com/projects/g/systemd/systemd/alerts/?mode=tre...

(full disclosure, I also work at Semmle)

Re:Coverity Scan Update by paulmelnikow on Friday January 11, 2019 @12:57PM (#18885338)
We use it in https://shields.io/ for JavaScript. It finds semantic bugs that are really hard for humans to find. I think it especially shines at finding problems in old code. Yes, old code is good code, though it may not be secure. Also unused code, like React state that is set but never read.

I used it for Nock, too, to make some quick fixes: https://github.com/nock/nock/pull/1301/files

In Shields we have the PR app turned on and it keeps us alert to problems during the review process. It's slower than CI, though usually problems manifest early enough in the review process that they can be fixed before merge.