dbcve.org
CcagentApplication · Alcatel Lucent

CVE-2010-3280

MEDIUM · 6.9 CVSS v2.0 Published 2010-09-23
Fix available
A fix is available. Upgrade to after 8.0 or later.
See remediation →
74/100
Remediation priority · Elevated
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 CCAgent option 9.0.8.4 and earlier in the management server (aka TSA) component in Alcatel-Lucent OmniTouch Contact Center Standard Edition relies on client-side authorization checking, and unconditionally sends the SuperUser password to the client for use during an authorized session, which allows remote attackers to monitor or reconfigure Contact Center operations via a modified client application.

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

The CCAgent component in Alcatel-Lucent OmniTouch Contact Center Standard Edition (versions 9.0.8.4 and earlier) relies on client-side authorization checks and unconditionally transmits the SuperUser password to the client during authorized sessions. This design flaw allows remote attackers with a modified client application to bypass server-side authorization and monitor or reconfigure Contact Center operations.

MitigationApply vendor-supplied patches to upgrade beyond version 9.0.8.4, or if patches are unavailable (product EOL), implement network segmentation and monitor for unauthorized access attempts. Replace client-side authorization logic with proper server-side validation.

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
CcagentApplication
Affected:<= 8.0= 7.1
Omnitouch Contact CenterApplication
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
Adjacent
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Partial
Availability
Partial

AV:A/AC:M/Au:N/C:C/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. Identify if OmniTouch Contact Center or CCAgent is installed
    Look for installation directories (common paths: C:\Program Files\Alcatel-Lucent\ or C:\Alcatel\) or check running services for 'CCAgent', 'OmniTouch', or 'Contact Center' processes
    Affected if The product is present on the system
  2. Check CCAgent version
    Examine the CCAgent version through the application interface, installation directory version files, or Windows Add/Remove Programs. Affected versions are 7.1, 8.0 and earlier, or any version of OmniTouch Contact Center
    Affected if Version is 7.1, 8.0 or earlier, or if using OmniTouch Contact Center of any version
  3. Determine if CCAgent is network-accessible
    Check if CCAgent ports (typically TCP 4242, 4243, or service-specific ports) are listening on interfaces accessible from outside the local network using netstat or port scanning tools
    Affected if CCAgent service ports are exposed to untrusted networks
  4. Inspect CCAgent authorization configuration
    Examine CCAgent configuration files (typically in the CCAgent config directory) for settings that indicate client-side authorization is enabled, such as 'ClientAuthorization', 'AllowClientOverride', or similar flags
    Affected if Client-side authorization checks are configured or enabled in CCAgent settings
  5. Check for SuperUser account exposure
    Review CCAgent logs or configuration for transmission of SuperUser credentials to client machines, or examine network traffic between CCAgent server and clients if accessible
    Affected if SuperUser password is being transmitted to client stations during normal operation

A defender is affected if they have OmniTouch Contact Center of any version or CCAgent versions 7.1 through 8.0 installed, with CCAgent network services exposed and client-side authorization in use.

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
Upgrade available Upgrade to a release after 8.0
Interim mitigation

Apply vendor-supplied patches to upgrade beyond version 9.0.8.4, or if patches are unavailable (product EOL), implement network segmentation and monitor for unauthorized access attempts. Replace client-side authorization logic with proper server-side validation.

Fix this in Ccagent Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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