Video Surveillance Operations ManagerApplication · Cisco
CVE-2014-0674
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 · uneditedCisco Video Surveillance Operations Manager (VSOM) does not require authentication for MySQL database connections, which allows remote attackers to obtain sensitive information, modify data, or cause a denial of service by leveraging network connectivity from a client system with a crafted host name, aka Bug ID CSCud10992.
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 confidenceCisco Video Surveillance Operations Manager (VSOM) ships with MySQL database connections configured without authentication required. An attacker with network connectivity to the database server can connect anonymously to read sensitive surveillance data, modify records, or disrupt service via DoS.
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
Video Surveillance Operations ManagerApplication
all versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine if Cisco VSOM is installedCheck for the presence of Cisco Video Surveillance Operations Manager software in your environment. Look for VSOM processes, services, or installed directories.Affected if VSOM is installed and running in the environment
-
Identify the MySQL database configurationLocate the MySQL configuration files or connection settings used by VSOM. Check database connection parameters for authentication credentials.Affected if MySQL connection strings lack username/password or use blank/default authentication credentials
-
Test MySQL connectivity without credentialsAttempt to connect to the VSOM MySQL database from a system with network access using a MySQL client without providing any credentials (e.g., mysql -h <target_ip>).Affected if The connection succeeds without authentication
-
Check MySQL user permissionsOnce connected, execute 'SELECT user, host, authentication_string FROM mysql.user' to list database users and verify if anonymous or root accounts exist without passwords.Affected if Anonymous accounts exist or password authentication is not enforced
-
Verify network exposure of database portCheck if the MySQL port (default 3306) used by VSOM is accessible from untrusted networks or directly from the internet using port scanning or firewall rules review.Affected if The MySQL port is accessible from outside the trusted network segment
If Cisco VSOM is running and its MySQL database accepts connections without authentication or is network-accessible without controls, the environment is affected by this vulnerability.
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.
From vendor dataEnable MySQL authentication by configuring secure credentials for database connections and restrict network access to the database port via firewall rules or network segmentation.
Fix this in Video Surveillance Operations Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0674 — 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-2014-0674 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