dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2016-15046

HIGH · 8.6 CVSS v4.0 Published 2025-07-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable No privileges

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
A client-side remote code execution vulnerability exists in Hanwha Techwin Smart Security Manager (SSM) versions 1.32 and 1.4, due to improper restrictions on the PUT method exposed by the bundled Apache ActiveMQ instance (running on port 8161). An attacker can exploit this flaw through a Cross-Origin Resource Sharing (CORS) bypass combined with JavaScript-triggered file uploads to the web server, ultimately resulting in arbitrary code execution with SYSTEM privileges. This vulnerability bypasses the server-side mitigations introduced in ZDI-15-156 and ZDI-16-481 by shifting the exploitation to the client-side. This product is now referred to as Hanwha Wisenet SSM and it is unknown if current versions are affected.

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 · moderate confidence

Client-side RCE in Hanwha Techwin SSM (versions 1.32, 1.4) via bundled Apache ActiveMQ on port 8161. Improper PUT method restrictions combined with CORS bypass and JavaScript-triggered file uploads allow arbitrary code execution with SYSTEM privileges, bypassing prior server-side mitigations.

MitigationRestrict or disable the PUT method on the Apache ActiveMQ web console, implement proper CORS restrictions, and consider network segmentation to limit access to port 8161; if available, upgrade to a fixed version of Hanwha Wisenet SSM.

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
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/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. Confirm Hanwha Techwin SSM installation
    Check for SSM installation directories or running processes on the system. Common paths include C:\Program Files\Hanwha\ or C:\SmartSecurityManager\. Look for processes named 'SSM.exe' or 'SmartSecurityManager.exe' in running processes.
    Affected if Hanwha Techwin SSM software is present on the system
  2. Identify SSM version
    Open the SSM application, navigate to Help > About, or check the version listed in the installed program's properties. Alternatively, examine the executable file properties of the main SSM binary.
    Affected if The installed version is 1.32 or 1.4, as these are the affected versions listed in the CVE
  3. Verify ActiveMQ web console accessibility
    Attempt to access http://localhost:8161 or the system's IP on port 8161 from a browser or via curl: curl http://<target>:8161
    Affected if The ActiveMQ web console is accessible on port 8161 (internal or external network)
  4. Check HTTP PUT method enabled
    Send a PUT request to the ActiveMQ web console using curl: curl -X PUT http://<target>:8161/api/test -v
    Affected if The server accepts and processes PUT requests (HTTP 200 or 204 response rather than 405 Method Not Allowed)
  5. Inspect CORS configuration
    Send a request with an Origin header and check the response headers: curl -H "Origin: http://malicious-site.com" http://<target>:8161 -I | grep -i cors
    Affected if The server returns Access-Control-Allow-Origin headers that allow arbitrary origins, or lacks proper origin validation

A system is affected if Hanwha Techwin SSM versions 1.32 or 1.4 are installed with the bundled ActiveMQ web console on port 8161 accessible and both the PUT method and improper CORS headers are present.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict or disable the PUT method on the Apache ActiveMQ web console, implement proper CORS restrictions, and consider network segmentation to limit access to port 8161; if available, upgrade to a fixed version of Hanwha Wisenet SSM.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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