dbcve.org
ScrutinizerApplication · Sonicwall

CVE-2012-2627

HIGH · 9.4 CVSS v2.0 Published 2012-07-31
Fix available
A fix is available. Upgrade to 9.5.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
d4d/uploader.php in the web console in Plixer Scrutinizer (aka Dell SonicWALL Scrutinizer) before 9.5.0 allows remote attackers to create or overwrite arbitrary files in %PROGRAMFILES%\Scrutinizer\snmp\mibs\ via a multipart/form-data POST request.

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

Arbitrary file upload vulnerability in d4d/uploader.php in Plixer Scrutinizer web console versions before 9.5.0 allows remote unauthenticated attackers to write arbitrary files to the %PROGRAMFILES%\Scrutinizer\snmp\mibs\ directory via specially crafted multipart/form-data POST requests.

MitigationUpgrade to Scrutinizer version 9.5.0 or later which contains the patch. If immediate patching is not possible, restrict network access to the web console and disable or protect the uploader.php endpoint via web server configuration.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ScrutinizerApplication
Affected:< 9.5.0

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
Authentication
None
Confidentiality
None
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:C/A:C

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. Identify if Scrutinizer is installed
    Check for the presence of Scrutinizer installation directory at %PROGRAMFILES%\Scrutinizer or look for IIS/web server hosting the Scrutinizer web console
    Affected if Scrutinizer web console software is present on the system
  2. Determine the installed Scrutinizer version
    Look for version information in the web console interface, check for a README, VERSION file, or examine the application binaries/dlls for version metadata
    Affected if The installed version is any version before 9.5.0
  3. Verify the vulnerable uploader.php exists
    Check if the file d4d/uploader.php exists in the web root of the Scrutinizer installation
    Affected if The file d4d/uploader.php is present and accessible via the web server
  4. Confirm the target upload directory is writable
    Verify the directory %PROGRAMFILES%\Scrutinizer\snmp\mibs\ exists and check if the web server process has write permissions to it
    Affected if The mibs directory exists and is writable by the web application
  5. Check if the web console is network-exposed
    Review firewall rules and web server bindings to determine if the Scrutinizer web interface is accessible from untrusted networks
    Affected if The web console is accessible from outside the local network or untrusted hosts

The environment is affected if Scrutinizer web console is installed with a version below 9.5.0 and the d4d/uploader.php endpoint is accessible, allowing unauthenticated file upload to the snmp/mibs directory.

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
Upgrade available Upgrade to 9.5.0 or later
Fixed in 9.5.0
Interim mitigation

Upgrade to Scrutinizer version 9.5.0 or later which contains the patch. If immediate patching is not possible, restrict network access to the web console and disable or protect the uploader.php endpoint via web server configuration.

Recommended fix Moderate confidence

9.5.0 or later

  1. Back up the current Scrutinizer installation and database before upgrading
  2. Download Scrutinizer version 9.5.0 or later from the official Plixer website (www.plixer.com)
  3. Stop the Scrutinizer services if running
  4. Install the updated version following the vendor's upgrade documentation
  5. Restart the Scrutinizer services
  6. Verify the d4d/uploader.php file has been updated or removed and the vulnerability is patched

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

Fix this in Scrutinizer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-2627 — 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-2012-2627 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