Ciscoworks Common ServicesApplication · Cisco
CVE-2011-2042
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 · uneditedThe Sybase SQL Anywhere database component in Cisco CiscoWorks Common Services 3.x and 4.x before 4.1 allows remote attackers to obtain potentially sensitive information about the engine name and database port via an unspecified request to UDP port 2638, aka Bug ID CSCsk35018.
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 confidenceThe Sybase SQL Anywhere database component in CiscoWorks Common Services versions 3.x and 4.x before 4.1 exposes sensitive database information (engine name and database port) via unsolicited UDP requests to port 2638. This information disclosure vulnerability allows remote unauthenticated attackers to gather reconnaissance data about the database infrastructure.
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
Ciscoworks Common ServicesApplication
= 3.0= 3.0.3= 3.0.4= 3.0.5= 3.0.6= 3.1= 3.1.1= 3.2= 3.3= 4.0.1CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify CiscoWorks Common Services installationLocate the CiscoWorks Common Services installation on the system. On Windows, check for C:\CiscoWorks directory. On Linux/Unix, check for /opt/CSCOpx or /usr/local/cisco directory. Alternatively, use system inventory tools to list installed software containing 'CiscoWorks' or 'Common Services'.Affected if CiscoWorks Common Services is not installed on the system
-
Determine the installed versionLocate the version file within the CiscoWorks installation directory, typically found in version.txt or via the application's about/release notes. Compare your version against the affected list: 3.0, 3.0.3, 3.0.4, 3.0.5, 3.0.6, 3.1, 3.1.1, 3.2, 3.3, and 4.0.1.Affected if The installed version matches any of these: 3.0, 3.0.3, 3.0.4, 3.0.5, 3.0.6, 3.1, 3.1.1, 3.2, 3.3, or 4.0.1
-
Check if UDP port 2638 is listeningRun netstat -an or ss -anu on the system to verify if UDP port 2638 is in LISTENING state. Use 'netstat -an | findstr 2638' on Windows or 'netstat -anu | grep 2638' on Linux/Unix. This port hosts the Sybase SQL Anywhere database listener.Affected if UDP port 2638 is open and listening on the system
You are affected if CiscoWorks Common Services version 3.0 through 4.0.1 is installed AND UDP port 2638 is exposed (listening), allowing remote attackers to send unsolicited UDP queries that disclose database engine name and port information.
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 dataUpgrade CiscoWorks Common Services to version 4.1 or later, or restrict network access to UDP port 2638 via firewall rules to prevent unauthorized external queries.
Fix this in Ciscoworks Common Services
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2042 — 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-2011-2042 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