dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2011-10017

CRITICAL · 10.0 CVSS v4.0 Published 2025-08-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Snort Report versions < 1.3.2 contains a remote command execution vulnerability in the nmap.php and nbtscan.php scripts. These scripts fail to properly sanitize user input passed via the target GET parameter, allowing attackers to inject arbitrary shell commands. Exploitation requires no authentication and can result in full compromise of the underlying system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Snort Report versions before 1.3.2 contain an unauthenticated remote command execution vulnerability in nmap.php and nbtscan.php. Attackers can inject arbitrary shell commands through the unsanitized 'target' GET parameter, leading to full system compromise.

MitigationUpgrade to Snort Report 1.3.2 or later, or implement strict input validation/sanitization on the 'target' GET parameter in both affected scripts to prevent command injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Snort Report installation and identify version
    Search web server document roots for 'snortreport' directory, check for version.php or VERSION file within the installation, or inspect HTTP headers/banner when accessing the application
    Affected if Version is found to be before 1.3.2 or version cannot be determined
  2. Check if nmap.php exists
    Search for nmap.php in the Snort Report web directory (commonly /snortreport/ or /var/www/html/snortreport/)
    Affected if File exists in the installation directory
  3. Check if nbtscan.php exists
    Search for nbtscan.php in the Snort Report web directory
    Affected if File exists in the installation directory
  4. Inspect nmap.php for vulnerable 'target' parameter handling
    Open nmap.php in a text editor or use grep to search for 'target' GET parameter usage without sanitization functions (such as escapeshellcmd, escapeshellarg, or explicit input validation)
    Affected if The 'target' parameter is used in shell commands without proper sanitization (e.g., direct inclusion in exec, system, shell_exec calls)
  5. Inspect nbtscan.php for vulnerable 'target' parameter handling
    Open nbtscan.php in a text editor or use grep to search for 'target' GET parameter usage without sanitization functions
    Affected if The 'target' parameter is used in shell commands without proper sanitization

Affected if Snort Report version is before 1.3.2 AND either nmap.php or nbtscan.php is present with unsanitized 'target' parameter handling in shell command execution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Snort Report 1.3.2 or later, or implement strict input validation/sanitization on the 'target' GET parameter in both affected scripts to prevent command injection.

Recommended fix Moderate confidence

Snort Report 1.3.2 or later

  1. Identify the current version of Snort Report installed on the system
  2. If the installed version is less than 1.3.2, download Snort Report version 1.3.2 or the latest stable version from a trusted source such as the official project repository
  3. Back up the existing Snort Report installation and configuration files before upgrading
  4. Extract and deploy the new version, ensuring all configuration files are properly migrated
  5. Restart the web server (Apache, Nginx, or the relevant web server serving Snort Report) to apply changes
  6. Verify that the nmap.php and nbtscan.php scripts are no longer vulnerable by confirming the 'target' parameter is properly sanitized and does not allow command injection
  7. Test basic functionality to ensure Snort Report operates normally after the upgrade
Caveat Review any configuration changes required between your current version and 1.3.2; test in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-10017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-10017 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data