dbcve.org
Secure Access Link GatewayApplication · Avaya

CVE-2011-3008

MEDIUM · 5.0 CVSS v2.0 Published 2011-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
The default configuration of Avaya Secure Access Link (SAL) Gateway 1.5, 1.8, and 2.0 contains certain domain names in the Secondary Core Server URL and Secondary Remote Server URL fields, which allows remote attackers to obtain sensitive information by leveraging administrative access to these domain names, as demonstrated by alarm and log information.

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

Avaya Secure Access Link Gateway versions 1.5, 1.8, and 2.0 ship with default configuration values that include sensitive domain names in the Secondary Core Server URL and Secondary Remote Server URL fields. These domain names are exposed in alarm and log data, allowing attackers with administrative access to the referenced domains to obtain sensitive information.

MitigationModify the default Secondary Core Server URL and Secondary Remote Server URL fields in the SAL Gateway configuration to remove or replace the sensitive domain names with appropriate non-sensitive values, then verify that alarm and log outputs no longer expose this information.

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 Access Link GatewayApplication
Affected:= 1.5= 1.8= 2.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Avaya SAL Gateway version
    Locate the installed version of Avaya Secure Access Link Gateway in the system or administrative interface, or run the appropriate command to query the installed software version.
    Affected if The installed version is 1.5, 1.8, or 2.0 specifically.
  2. Check Secondary Core Server URL configuration
    Access the SAL Gateway configuration panel or configuration file and inspect the value of the Secondary Core Server URL field.
    Affected if The field contains a sensitive domain name that has not been modified from the default value.
  3. Check Secondary Remote Server URL configuration
    Access the SAL Gateway configuration panel or configuration file and inspect the value of the Secondary Remote Server URL field.
    Affected if The field contains a sensitive domain name that has not been modified from the default value.
  4. Examine alarm output for domain exposure
    Review alarm data or alarm log files generated by the SAL Gateway and search for any occurrences of the domain names present in the Secondary Core Server URL or Secondary Remote Server URL fields.
    Affected if Alarm output displays the sensitive domain names from these configuration fields.
  5. Examine general log output for domain exposure
    Review system or application log files from the SAL Gateway and search for any occurrences of the domain names present in the Secondary Core Server URL or Secondary Remote Server URL fields.
    Affected if Log output displays the sensitive domain names from these configuration fields.

The environment is affected if running version 1.5, 1.8, or 2.0 AND the default Secondary Core Server URL or Secondary Remote Server URL values have not been changed, resulting in sensitive domain names appearing in alarm or log outputs.

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

Modify the default Secondary Core Server URL and Secondary Remote Server URL fields in the SAL Gateway configuration to remove or replace the sensitive domain names with appropriate non-sensitive values, then verify that alarm and log outputs no longer expose this information.

Fix this in Secure Access Link Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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