CVE-2015-3435
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 · uneditedSamsung Security Manager (SSM) before 1.31 allows remote attackers to execute arbitrary code by uploading a file with an HTTP (1) PUT or (2) MOVE 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 · moderate confidenceSamsung Security Manager versions prior to 1.31 contain an insecure direct object reference or missing authentication vulnerability in their HTTP file upload functionality. Attackers can use HTTP PUT or MOVE requests to upload arbitrary files to the server, which can then be executed to achieve remote code execution with the privileges of the web service.
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<= 1.30CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Samsung Security Manager versionLocate the installed Samsung Security Manager instance and check its version number through the software interface, about dialog, or version information in the installation directory. Compare this version against the affected range (1.30 and below).Affected if The installed version is 1.30 or lower.
-
Verify HTTP PUT method is enabledSend an HTTP PUT request to the Samsung Security Manager web interface endpoint (typically the same URL used for the management console). Observe whether the server accepts the PUT method without returning a 405 Method Not Allowed or 403 Forbidden error.Affected if The server accepts PUT requests and returns a successful response (200 OK or 201 Created).
-
Verify HTTP MOVE method is enabledSend an HTTP MOVE request to the Samsung Security Manager web interface. Observe whether the server accepts the MOVE method without rejecting it.Affected if The server accepts MOVE requests and returns a successful response.
-
Inspect web directories for unauthorized filesExamine the web root and upload directories of the Samsung Security Manager application for any unexpected or malicious files, particularly executable files (ASP, ASPX, JSP, PHP, exe, dll) that were not intentionally deployed.Affected if Unexpected executable files exist in web-accessible directories that were not uploaded by authorized administrators.
If Samsung Security Manager version is 1.30 or lower AND the HTTP PUT or MOVE methods are accepted by the web server, the environment is vulnerable to unauthenticated file upload and potential remote code execution.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Samsung Security Manager to version 1.31 or later. If immediate patching is not possible, restrict HTTP PUT/MOVE methods at the network level (WAF or reverse proxy) and audit for any unauthorized files on the server.
1.31
- Upgrade Samsung Security Manager to version 1.31 or later
- Verify the upgrade was successful by checking the software version
- Test that the HTTP PUT and MOVE request functionality now properly validates uploaded files
- Confirm the arbitrary code execution vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3435 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-3435 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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