CVE-2011-1174
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 · uneditedmanager.c in Asterisk Open Source 1.6.1.x before 1.6.1.24, 1.6.2.x before 1.6.2.17.2, and 1.8.x before 1.8.3.2 allows remote attackers to cause a denial of service (CPU and memory consumption) via a series of manager sessions involving invalid data.
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 confidenceA resource exhaustion vulnerability in the Asterisk Manager Interface (manager.c) allows remote attackers to cause excessive CPU and memory consumption by sending a series of manager sessions containing invalid data, leading to denial of service.
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.6.1= 1.6.1.0= 1.6.1.1= 1.6.1.2= 1.6.1.3= 1.6.1.4= 1.6.1.5= 1.6.1.6= 1.6.1.7= 1.6.1.8= 1.6.1.9= 1.6.1.10CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Asterisk is installedRun 'asterisk -V' or 'asterisk -vvv' to display version information, or check package manager (rpm -q asterisk, dpkg -l | grep asterisk)Affected if No Asterisk installed means not affected
-
Verify the installed Asterisk versionCompare the version output from step 1 against the affected range: 1.6.1.0 through 1.6.1.10 (including 1.6.1)Affected if Version falls within 1.6.1.x series up to 1.6.1.10, user is potentially affected
-
Determine if Asterisk Manager Interface (AMI) is enabledCheck /etc/asterisk/manager.conf for 'enabled = yes' in the [general] section, or check if AMI module (res_manager.so) is loaded via 'module show' in Asterisk CLIAffected if AMI is disabled or not loaded, the specific vulnerability in manager.c is not exploitable
-
Check if manager port is accessible from networkVerify port 5038 (default AMI port) is listening and accessible externally: run 'netstat -tlnp | grep 5038' or 'ss -tlnp | grep 5038', then determine if firewall or ACLs restrict accessAffected if Port 5038 is exposed to untrusted networks without restrictions, remote attackers can exploit the vulnerability
User is affected if running Asterisk version 1.6.1.x (1.6.1 through 1.6.1.10) with AMI enabled and port 5038 accessible to untrusted networks.
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.
From vendor dataUpgrade Asterisk to version 1.6.1.24, 1.6.2.17.2, 1.8.3.2 or later. Additionally, restrict network access to the manager port (default 5038) using firewalls or ACLs, and implement rate limiting on AMI connections.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1174 — 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-1174 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