CVE-2011-5096
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 · uneditedStack-based buffer overflow in cstore.exe in the Media Application Server (MAS) in Avaya Aura Application Server 5300 (formerly Nortel Media Application Server) 1.x before 1.0.2 and 2.0 before Patch Bundle 10 allows remote attackers to execute arbitrary code via a crafted cs_anams parameter in a CONTENT_STORE_ADMIN_REQ packet.
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 confidenceStack-based buffer overflow in cstore.exe allows remote attackers to execute arbitrary code via a crafted cs_anams parameter in CONTENT_STORE_ADMIN_REQ packets. The vulnerability exists in the Media Application Server component of Avaya Aura Application Server 5300 (formerly Nortel MAS) versions 1.x before 1.0.2 and 2.0 before Patch Bundle 10.
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= 1.0= 2.0CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/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 Avaya Aura Application Server 5300 installationLocate the Media Application Server component on the system or check installed programs for Avaya Aura Application Server 5300 (formerly Nortel MAS). Query the system inventory or installed software list for this product.Affected if The product is installed and running on the system.
-
Determine installed versionCheck the installed version of Avaya Aura Application Server 5300. For version 1.x, verify it is below 1.0.2. For version 2.0, verify it is below Patch Bundle 10. Compare your version against these thresholds.Affected if The installed version is 1.x before 1.0.2 OR version 2.0 before Patch Bundle 10.
-
Locate vulnerable component cstore.exeSearch for the file cstore.exe in the Media Application Server installation directory. This is the executable that contains the vulnerable code handling the cs_anams parameter.Affected if The cstore.exe file exists on the system.
-
Verify CONTENT_STORE_ADMIN_REQ service accessibilityIdentify the port or service handling CONTENT_STORE_ADMIN_REQ packets. Check if this service is exposed to network access. Review firewall rules and service configuration for the Media Application Server component.Affected if The CONTENT_STORE_ADMIN_REQ service is network-accessible to untrusted sources.
You are affected if Avaya Aura Application Server 5300 is installed with version 1.x before 1.0.2 or version 2.0 before Patch Bundle 10, and the cstore.exe component handling CONTENT_STORE_ADMIN_REQ packets is accessible on the network.
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.
dbcve · scopedApply vendor patches (version 1.0.2 or Patch Bundle 10) to fix the buffer overflow; if patching is not immediately feasible, network-segment the MAS service and block external access to the CONTENT_STORE_ADMIN_REQ port.
Version 1.0.2 for 1.x branch; Patch Bundle 10 for 2.0 branch
- 1. Identify the currently installed version of Avaya Aura Application Server 5300 (1.x or 2.0) by checking the system configuration or About section.
- 2. For version 1.x users: Upgrade to version 1.0.2 or later which contains the security fix for the cstore.exe buffer overflow.
- 3. For version 2.0 users: Apply Patch Bundle 10 or later to address the vulnerability.
- 4. Obtain the update from the official Avaya support portal at downloads.avaya.com or contact Avaya technical support.
- 5. Before applying the upgrade, backup all configuration data and ensure the system meets any prerequisites.
- 6. Apply the upgrade following the standard Avaya upgrade procedures documented in the installation guide.
- 7. After upgrade, verify the cstore.exe component has been updated and restart the Media Application Server service.
- 8. Validate that the CONTENT_STORE_ADMIN_REQ functionality continues to operate normally.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-5096 — 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-2011-5096 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