cve-search | perform local searches for known vulnerabilities | Security Testing library
kandi X-RAY | cve-search Summary
kandi X-RAY | cve-search Summary
[Join the chat at cve-search is a tool to import CVE (Common Vulnerabilities and Exposures) and CPE (Common Platform Enumeration) into a MongoDB to facilitate search and processing of CVEs. The main objective of the software is to avoid doing direct and public lookups into the public CVE databases. Local lookups are usually faster and you can limit your sensitive queries via the Internet. cve-search includes a back-end to store vulnerabilities and related information, an intuitive web interface for search and managing vulnerabilities, a series of tools to query the system and a web API interface. cve-search is used by many organizations including the [public CVE services of CIRCL] This document gives you basic information how to start with cve-search. For more information please refer to the documentation in the /doc folder of this project.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Create a Flask application
- Returns the CORS allowed CORS settings
- Return a redis token connection
- Read a setting
- Download a site
- Store the content of the given response content
- Sanitize an object
- Return a session object
- Start the application
- Create the Flask application
- Process a file to queue
- Populate the cve database
- Pretty print CVE data
- Retrieves the CPE for a given cveid
- Load authentication methods
- Process a file
- Validate a user against the local database
- Return the VERSION tag
- Create indexes
- Handle the progress bar
- Login to IDP
- Process the collection
- Handle login
- Add a new item
- Process the request
- Start fetch processing
- List all available products
cve-search Key Features
cve-search Examples and Code Snippets
» python3 search.py -h
usage: search.py [-h] [-s] -y YEAR [-c COUNT] search
positional arguments:
search Search query (regex capable)
optional arguments:
-h, --help show this help message and exit
-s, --short
Surfraw - Shell Users' Revolutionary Front Rage Against the Web
______ _ _ ______ _______ ______ _______ _ _ _
/ _____)(_) (_)(_____ \ (_______)(_____ \ (_______)(_)(_)(_)
( (____ _ _ _____) ) _____ _____) ) __
Surfraw - Shell Users' Revolutionary Front Rage Against the Web
______ _ _ ______ _______ ______ _______ _ _ _
/ _____)(_) (_)(_____ \ (_______)(_____ \ (_______)(_)(_)(_)
( (____ _ _ _____) ) _____ _____) ) __
Community Discussions
Trending Discussions on Security Testing
QUESTION
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:04I 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.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install cve-search
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page