sast-scan | Open Source DevSecOps tool for performing static analysis | Security Testing library

by ShiftLeftSecurity Python Version: v2.1.1 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | sast-scan Summary

sast-scan is a Python library typically used in Testing, Security Testing, Docker applications. sast-scan has no vulnerabilities, it has build file available and it has low support. However sast-scan has 216 bugs and it has a Non-SPDX License. You can download it from GitHub.

Scan is a free open-source security tool for modern DevOps teams. With an integrated multi-scanner based design, Scan can detect various kinds of security flaws in your application, and infrastructure code in a single fast scan without the need for any remote server. Scan is purpose built for workflow integration with nifty features such as automatic build breaker, results baseline and PR summary comments. Scan products are open-source under a GNU GPL 3.0 or later (GPL-3.0-or-later) license.

Support

Quality

Security

License

Reuse

Support

sast-scan has a low active ecosystem.

It has 622 star(s) with 101 fork(s). There are 31 watchers for this library.

It had no major release in the last 12 months.

There are 42 open issues and 76 have been closed. On average issues are closed in 28 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of sast-scan is v2.1.1

Quality

sast-scan has 216 bugs (1 blocker, 0 critical, 0 major, 215 minor) and 273 code smells.

Security

sast-scan has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

sast-scan code analysis shows 0 unresolved vulnerabilities.

There are 15 security hotspots that need review.

License

sast-scan has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

sast-scan releases are available to install and integrate.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

It has 19335 lines of code, 611 functions and 96 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed sast-scan and discovered the below as its top functions. This is intended to give you an instant insight into sast-scan implemented functionality, and help decide if they suit your requirements.

Check for common errors
Get assignments as a dictionary
Prepare a pattern
Generate AST nodes that match this pattern
Generate a summary summary report
Calculate the usage metrics for the depscan
Get list of depscan data
Check common misconfig files
Returns a list of Constant objects
Handles imports
Visit arguments
Parse the XML file
Check if the given function is a taintable function
Check for common misconfiguration
Visitor for assignments
Prepare the given pattern
Handles POST request
Visit a Try node
Return a dict representation of the issue
Inspect a source scan
Check for unsafe misconfiguration
Detect the project type
Check common misconfiguredis
Annotate a pull request
Execute default command
Annotate a scan
Deep analysis of files

Get all kandi verified functions for this library.

sast-scan Key Features

No Key Features are available at this moment for sast-scan.

sast-scan Examples and Code Snippets

No Code Snippets are available at this moment for sast-scan.

Community Discussions

Trending Discussions on Security Testing

DAST security scaning of a IoT Nodemcu esp8266 LUA script www HTML server connected to camera and A/C relay

QUESTION

DAST security scaning of a IoT Nodemcu esp8266 LUA script www HTML server connected to camera and A/C relay

Asked 2021-Apr-08 at 01:04

I have not, but shall DAST* security test, out of curiosity, an IoT device; Nodemcu esp8266 www server I built. It's showing a HTML page (on a mobile phone for example) that allows to control and interact with a camera module and a A/C relay. With it I can for example show images captured in the camera I even think it has some image recognition built in, and I can switch on and off a relay for electrical current to a light bulb (110/220v A/C power)

Before I start pentest I though I better start thinking of what types of exploits one would be able to find and detect? Which sinister exploits I will be able to find, or rather ought be able to find given a proper pentest exercise? (And if I do not find exploits, my approach to the pentest of the Iot might be wrong)

I ponder it might be a totally pointless exercise since the esp8266 www server (or rather its LUA programming libraries) might not have any security built into it, so basically it is "open doors" and everything with it is unsafe ?

The test report might just conclude what I can foresee be that the the "user input needs to be sanitized"?

Anyone have any idea what such pentest of a generic IoT device generally reports? Maybe it is possible to crash or reset the IoT device? Buffer overruns, XXS, call own code ?

I might use ZAP or Burpsuite or similar DAST security test tool.

I could of course SAST test it instead, or too, but I think it will be hard to find a static code analyzer for the NodeMCU libraries and NUA scripting language easily ? I found some references here though: https://ieeexplore.ieee.org/abstract/document/8227299 but it seems to be a long read.

So if someone just have a short answer what to expect in a DAST scan/pentest , it would be much appreciated.

Stay safe and secure out there ! Zombieboy

...

ANSWER

Answered 2021-Apr-08 at 01:04

I do my vulnerability scanning with OpenVAS (I assume this is what you mean by pentesting?). I am not aware of any IOT focused Tools.

If your server is running on esp8266, i would imagine that there is no much room for authentication and encryption of http traffic, but correct me if i am wrong).

Vulnerability Scan results might show things like unencrypted http traffic, credentials transmitted in cleartext (if you have any credentials fields in the pages served by the web server) etc. Depending on if there is encryption, you might also see weak encryption findings.

You might get some false positives on your lua webserver reacting like other known webservers when exploits are applied. I have seen this kind of false positive specially on DoS vulnerabilities when a vulnerability scan is testing a vulnerability and the server becomes unresponsive. Depending on how invasive your vulnerability scanner is, you might get a lot of false positives for DoS on such a constrained platform.

Source https://stackoverflow.com/questions/66995125

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install sast-scan

scan is ideal for use with CI and also as a pre-commit hook for local development. Scan is distributed as a container image shiftleft/scan, and as an AppImage for supported Linux distributions.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: