dbcve.org
Secure Global DesktopApplication · Sun

CVE-2006-4958

MEDIUM · 6.8 CVSS v2.0 Published 2006-09-23
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
Multiple cross-site scripting (XSS) vulnerabilities in Sun Secure Global Desktop (SSGD, aka Tarantella) before 4.20.983 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors, possibly involving (1) taarchives.cgi, (2) ttaAuthentication.jsp, (3) ttalicense.cgi, (4) ttawlogin.cgi, (5) ttawebtop.cgi, (6) ttaabout.cgi, or (7) test-cgi. NOTE: This information is based upon a vague initial disclosure. Details will be updated as they become available.

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 confidence

Multiple cross-site scripting (XSS) vulnerabilities in Sun Secure Global Desktop (Tarantella) allow remote attackers to inject arbitrary web script or HTML through seven affected components: taarchives.cgi, ttaAuthentication.jsp, ttalicense.cgi, ttawlogin.cgi, ttawebtop.cgi, ttaabout.cgi, and test-cgi. The vulnerability exists in versions prior to 4.20.983.

MitigationUpgrade to Sun Secure Global Desktop version 4.20.983 or later; alternatively, implement input validation and output encoding on the affected CGI and JSP endpoints to neutralize malicious script injection.

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
Secure Global DesktopApplication
Affected:= 3.42= 4.0

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 Sun Secure Global Desktop installation
    Locate the Sun Secure Global Desktop or Tarantella installation on the system. Look for installation directories such as /opt/SUNWsgd, /opt/tarantella, or the product-specific installation path. Use commands like 'ls /opt' or check the system's software inventory.
    Affected if The product is not installed on the system.
  2. Identify the installed version
    Determine the installed version of Sun Secure Global Desktop. Check version files in the installation directory, or use product-specific commands if available. Common locations include version files or the product's about/version information pages accessible via the web interface.
    Affected if The installed version is 3.42, 4.0, or any version prior to 4.20.983.
  3. Verify presence of vulnerable CGI and JSP components
    Check for the existence of the seven affected components in the web server's CGI-bin or JSP directories. The affected files are: taarchives.cgi, ttaAuthentication.jsp, ttalicense.cgi, ttawlogin.cgi, ttawebtop.cgi, ttaabout.cgi, and test-cgi. These are typically found under the web interface document root.
    Affected if Any of these CGI or JSP files exist on the server.
  4. Confirm web interface accessibility
    Verify that the Sun Secure Global Desktop web interface is accessible and exposed. Check if the web server (typically on ports 443, 8443, or similar) is running and accepting connections. Attempt to access the affected endpoints via HTTP/HTTPS.
    Affected if The web interface is accessible remotely or internally.

A user is affected if Sun Secure Global Desktop (Tarantella) version 3.42, 4.0, or any version prior to 4.20.983 is installed and the web interface with the vulnerable CGI/JSP components is accessible.

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

Upgrade to Sun Secure Global Desktop version 4.20.983 or later; alternatively, implement input validation and output encoding on the affected CGI and JSP endpoints to neutralize malicious script injection.

Fix this in Secure Global Desktop Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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