We can detect vulnerabilities in server software and applications that expose network services and get information on software and version.
Vulnerability Detection Method
To detect vulnerabilities, we collect data from internet scans.
If data is insufficient to determine a vulnerability’s presence or the data is unavailable, we may deploy an active probe by triggering vulnerable code (without exploitation) or by checking if software behavior related to a vulnerability’s patch or mitigation is present.
The approach may vary as active probe detections are specific to the vulnerability that they detect.
Example:
- Checking if a request for a specific resource generates an error page.
- Checking if a specific resource is present that is removed once a patch is installed.
Mitigation Status Detection Method
Scans run continuously across the Internet. We compare iterations of these internet scans to determine if a vulnerability is patched and if the host is still vulnerable.
Limitations
We are unable to track most vulnerabilities in client devices (Android/iOS vulnerabilities, browser vulnerabilities, etc.) or systems and software exclusively used inside an organization.
Vulnerabilities must be safe to scan for, have viable data once scanned, and scanning activities must follow legalities.
We are unable to track:
- Scans requiring remote code execution.
- Scans requiring authentication or additional levels of access.
- Scans that may divulge information from the target system.
- Scans that may negatively impact normal operation on the target system.
Vulnerabilities relate only to identified with a designated CVE ID. They do not reflect any compromised systems, ransomware events, etc.
- April 17, 2025: Published.
Feedback
0 comments
Please sign in to leave a comment.