CVE-2010-3279
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 default configuration of the CCAgent option before 9.0.8.4 in the management server (aka TSA) component in Alcatel-Lucent OmniTouch Contact Center Standard Edition enables maintenance access, which allows remote attackers to monitor or reconfigure Contact Center operations via vectors involving TSA_maintenance.exe.
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 confidenceThe CCAgent component in Alcatel-Lucent OmniTouch Contact Center Standard Edition versions prior to 9.0.8.4 ships with maintenance access enabled by default in its configuration. This allows the TSA_maintenance.exe utility to be exploited by remote attackers to monitor or modify Contact Center operations without authentication.
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<= 8.0= 7.1all 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
- Adjacent
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Partial
- Availability
- Complete
AV:A/AC:M/Au:N/C:C/I:P/A:C
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 CCAgent or OmniTouch Contact Center installationLook for Alcatel-Lucent CCAgent or OmniTouch Contact Center Standard Edition software on the system. Check installed programs or look for the CCAgent installation directory.Affected if The software is installed and running on the system
-
Determine the installed versionFind the version of the CCAgent or OmniTouch Contact Center installation. This is typically available in the software itself, an about dialog, or in installation files.Affected if The version is 7.1, 8.0 or earlier, or any version of OmniTouch Contact Center (all versions are affected)
-
Locate and inspect the TSA configurationFind the TSA (Telephony Services Application) configuration files for CCAgent. Look for settings related to maintenance access or remote administration capabilities.Affected if Maintenance access is found to be enabled in the configuration
-
Check for TSA_maintenance.exe accessibilityLocate the TSA_maintenance.exe utility within the CCAgent installation directory. Determine if it is accessible and can be executed without authentication prompts.Affected if TSA_maintenance.exe exists and can be accessed or executed without requiring credentials
If OmniTouch Contact Center or CCAgent is installed, the version is 7.1 or 8.0 or earlier, and maintenance access is enabled in the TSA configuration, the environment is affected by CVE-2010-3279.
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 to CCAgent version 9.0.8.4 or later, or disable the maintenance access feature in the TSA configuration if upgrading is not feasible.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3279 — 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-2010-3279 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