Transport Gateway Installation SoftwareApplication · Cisco

CVE-2014-3345

MEDIUM · 5.0 CVSS v2.0 Published 2014-08-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/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
The web framework in Cisco Transport Gateway for Smart Call Home (aka TG-SCH or Transport Gateway Installation Software) 4.0 does not properly check authorization for administrative web pages, which allows remote attackers to modify the product via a crafted URL, aka Bug ID CSCuq31503.

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

The web framework in Cisco Transport Gateway for Smart Call Home 4.0 contains a broken access control vulnerability where administrative web pages fail to properly verify user authorization, allowing remote unauthenticated attackers to access and modify administrative functions via specially crafted URLs.

MitigationApply the vendor patch from Cisco for bug ID CSCuq31503. As a compensating control, restrict network access to the management interface using ACLs or VPN tunnels to limit exposure to untrusted networks.

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
Transport Gateway Installation SoftwareApplication
Affected:= 4.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
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/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. Identify if Cisco Transport Gateway for Smart Call Home is installed
    Locate the Cisco Transport Gateway installation and confirm the software name matches 'Cisco Transport Gateway for Smart Call Home' or 'Cisco Transport Gateway Installation Software'
    Affected if The software is not installed on the system
  2. Check the installed software version
    Use the application's built-in version display function, check the installation directory for version files, or query the software via its management interface to determine the exact version number
    Affected if The installed version is not 4.0 (exact match required - only 4.0 is affected)
  3. Verify the web management interface is accessible
    Attempt to reach the web interface via the management IP/hostname on typical HTTP/HTTPS ports (typically 80, 443, or configured management ports) or review network listener configuration
    Affected if The web interface is not accessible from the network being assessed
  4. Check for unauthorized administrative page access in logs
    Review web server logs, application logs, or security event logs for access attempts to administrative URLs (such as /admin, /configure, /settings, or similar paths) from unauthenticated or unauthorized IP addresses
    Affected if Evidence exists of unauthenticated access to administrative web pages or unusual administrative URL requests from unknown sources

The system is affected only if Cisco Transport Gateway for Smart Call Home version 4.0 is installed and its web management interface is network-accessible, allowing potential unauthenticated administrative access.

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 from Cisco for bug ID CSCuq31503. As a compensating control, restrict network access to the management interface using ACLs or VPN tunnels to limit exposure to untrusted networks.

Fix this in Transport Gateway Installation Software Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-3345 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-3345 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