dbcve.org
Broadband Access Center Telco Wireless SoftwareApplication · Cisco

CVE-2014-2190

MEDIUM · 6.8 CVSS v2.0 Published 2014-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
Cross-site request forgery (CSRF) vulnerability in the web framework in Cisco Broadcast Access Center for Telco and Wireless (aka BAC-TW) allows remote attackers to hijack the authentication of arbitrary users for requests that make BAC-TW changes, aka Bug IDs CSCuo23804 and CSCuo26389.

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

CSRF vulnerability in Cisco Broadcast Access Center for Telco and Wireless (BAC-TW) web framework allows remote attackers to hijack authenticated user sessions for unauthorized state-changing requests. Attackers can trick authenticated users into submitting malicious requests that perform configuration changes to the BAC-TW system.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing forms and validate tokens server-side; also apply SameSite cookie attributes and referrer validation as defense-in-depth.

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
Broadband Access Center Telco Wireless SoftwareApplication
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
Partial

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

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 BAC-TW installation
    Access the web interface of the system (typically on port 8080 or 8443) and verify you are on a Cisco Broadband Access Center Telco Wireless login page. Check the product name/version in the UI or check HTTP response headers for 'Cisco' and 'BAC-TW' identifiers.
    Affected if The system is running Cisco Broadband Access Center Telco Wireless Software - all versions are affected if no anti-CSRF protection exists.
  2. Inspect state-changing forms for CSRF tokens
    Log into the BAC-TW web interface and navigate to configuration pages that perform state changes (such as device provisioning settings, user management, or network configuration forms). View the HTML source of these forms and look for hidden input fields containing token values (commonly named 'csrf_token', 'token', 'anticsrf', or similar) or check if forms include token parameters in their action URLs.
    Affected if Forms lack hidden anti-CSRF token fields or token parameters in the form markup.
  3. Verify CSRF token validation on submission
    Submit a legitimate state-changing form request with a valid CSRF token, then attempt to submit the same form request without the token (or with a modified/invalid token) using a tool like curl or Burp Suite. Observe whether the application rejects requests missing or containing invalid tokens.
    Affected if The application accepts and processes requests without validating CSRF tokens.
  4. Check SameSite cookie attributes
    Log into the BAC-TW interface and use browser developer tools (Application tab > Cookies) or capture HTTP responses to examine the session cookies. Look for the 'SameSite' attribute on session-related cookies.
    Affected if Session cookies do not have SameSite=Strict or SameSite=Lax attributes configured.
  5. Check Referrer validation
    Capture HTTP requests when submitting state-changing forms. Observe if the application validates the Referer or Origin header on POST requests. Test by modifying or removing the Referer header in a request and see if the application accepts it.
    Affected if The application does not validate the Referrer or Origin header on state-changing requests.

If Cisco Broadband Access Center Telco Wireless is running and its state-changing web forms lack anti-CSRF token validation, the system is vulnerable to CVE-2014-2190.

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

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing forms and validate tokens server-side; also apply SameSite cookie attributes and referrer validation as defense-in-depth.

Fix this in Broadband Access Center Telco Wireless Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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