dbcve.org
Digital Media ManagerApplication · Cisco

CVE-2013-3446

MEDIUM · 5.8 CVSS v2.0 Published 2013-09-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
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
Open redirect vulnerability in the login page in Cisco Digital Media Manager (DMM) allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors, aka Bug ID CSCub23849.

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

The Cisco Digital Media Manager login page contains an open redirect vulnerability where the application fails to properly validate a redirect parameter. Attackers can craft malicious URLs that appear to originate from the legitimate DMM server but redirect users to arbitrary external websites, facilitating phishing attacks.

MitigationApply the vendor patch for CSCub23849. Until then, implement URL validation on the login redirect parameter to ensure only trusted domains are allowed, or disable the redirect functionality if not required.

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
Digital Media ManagerApplication
Affected:all versions

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

AV:N/AC:M/Au:N/C:P/I:P/A:N

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 Cisco Digital Media Manager is installed
    Check your system for Cisco DMM components. Common installation paths include /opt/cisco/dmm or C:\Program Files\Cisco\DM. Look for the DMM web application directory and the dmm.war file.
    Affected if Cisco DMM software is present on the system
  2. Identify the DMM login URL
    Locate the base URL for the DMM web interface. This is typically served on port 8443 or 443. Access the login page at /dm/login.do or the root path of the DMM web application.
    Affected if The DMM login page is accessible over the network
  3. Inspect the login page for redirect parameter
    Examine the HTML source of the login page or check the URL for a redirect parameter such as 'next', 'redirect', 'url', or 'target'. Also check HTML forms for hidden fields that control post-login redirection.
    Affected if A redirect parameter is present in the login URL or form
  4. Test redirect parameter behavior
    Construct a test URL with the redirect parameter set to an external domain (for example: https://your-dmm-server/dm/login.do?next=http://example.com). Observe whether the application accepts this external URL and would redirect to it after authentication.
    Affected if The application accepts and would process redirect URLs to external domains without validation
  5. Check for compensating controls
    Review any web application firewall (WAF) rules, reverse proxy configurations, or URL filtering that may block malicious redirect URLs. Check if the Cisco DMM login is behind an authentication proxy or SSO solution.
    Affected if No URL validation or compensating controls are in place to restrict the redirect parameter to trusted domains only

If Cisco Digital Media Manager is installed and the login page accepts an external URL in the redirect parameter without validation, the environment is affected by this open redirect vulnerability.

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

Apply the vendor patch for CSCub23849. Until then, implement URL validation on the login redirect parameter to ensure only trusted domains are allowed, or disable the redirect functionality if not required.

Fix this in Digital Media Manager 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-2013-3446 — 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-2013-3446 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