dbcve.org
AsteriskApplication

CVE-2008-1390

HIGH · 9.3 CVSS v2.0 Published 2008-03-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 AsteriskGUI HTTP server in Asterisk Open Source 1.4.x before 1.4.19-rc3 and 1.6.x before 1.6.0-beta6, Business Edition C.x.x before C.1.6, AsteriskNOW before 1.0.2, Appliance Developer Kit before revision 104704, and s800i 1.0.x before 1.1.0.2 generates insufficiently random manager ID values, which makes it easier for remote attackers to hijack a manager session via a series of ID guesses.

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 confidence

The AsteriskGUI HTTP server generates insufficiently random manager ID values, making it trivial for remote attackers to guess valid session IDs and hijack authenticated manager sessions. This is a cryptographically weak PRNG issue in the manager ID generation.

MitigationUpgrade Asterisk to patched versions (1.4.19-rc3+, 1.6.0-beta6+, or respective fixed releases for Business Edition/AsteriskNOW/ADK/s800i). If HTTP manager interface is unused, disable it as a compensating control.

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
AsteriskApplication
Affected:= 1.4.1= 1.4.2= 1.4.3= 1.4.4= 1.4.5= 1.4.6= 1.4.7= 1.4.8= 1.4.9= 1.4.10= 1.4.11= 1.4.12
Asterisk Appliance Developer KitApplication
Affected:= 0.2= 0.3= 0.4= 0.5= 0.6= 0.7= 0.8= 1.4
Asterisk Business EditionApplication
Affected:= c.1.0-beta7= c.1.0-beta8
AsterisknowApplication
Affected:= 1.0= beta_5= beta_6= beta_7
S800iApplication
Affected:= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.1.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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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 checks

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

  1. Identify Asterisk installation and version
    Run 'asterisk -V' or check your installed Asterisk package version using your system package manager
    Affected if The installed version matches 1.4.1 through 1.4.12, or one of the affected Appliance Developer Kit (0.2-1.4), Business Edition (c.1.0-beta7/c.1.0-beta8), AsteriskNOW (1.0, beta_5-beta_7), or S800i (1.0-1.1.0) versions
  2. Verify HTTP manager interface is enabled
    Check the manager.conf configuration file (typically in /etc/asterisk/) for the [general] section and look for 'enabled = yes' under HTTP settings
    Affected if The HTTP manager interface is enabled - this is required for remote attackers to reach the weak PRNG and attempt session hijacking
  3. Confirm manager interface is listening on network
    Check if the HTTP manager is bound to a network interface accessible remotely (not localhost-only) by examining the 'bindaddr' setting in manager.conf and verifying with 'netstat -tlnp | grep 5038' or similar
    Affected if The HTTP manager listens on a non-loopback interface, making it remotely exploitable
  4. Check for active manager sessions
    From the Asterisk CLI (asterisk -r), run 'manager show sessions' to see if any manager sessions are active over HTTP
    Affected if Active manager sessions exist over HTTP - an attacker could attempt to predict and hijack these session IDs

You are affected if you run a vulnerable Asterisk version AND have the HTTP manager interface enabled and accessible on a network, allowing attackers to exploit the weak session ID generation.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Asterisk to patched versions (1.4.19-rc3+, 1.6.0-beta6+, or respective fixed releases for Business Edition/AsteriskNOW/ADK/s800i). If HTTP manager interface is unused, disable it as a compensating control.

Recommended fix High confidence

Asterisk 1.4.19+ or 1.6.0-beta6+ (or respective fixed versions for Business Edition, AsteriskNOW, s800i, and Appliance Dev Kit)

  1. Identify the exact Asterisk product and version currently installed (Asterisk Open Source, Business Edition, AsteriskNOW, Appliance Developer Kit, or s800i)
  2. For Asterisk Open Source 1.4.x: Upgrade to version 1.4.19-rc3 or later (1.4.19-stable or later)
  3. For Asterisk Open Source 1.6.x: Upgrade to version 1.6.0-beta6 or later
  4. For Asterisk Business Edition C.x.x: Upgrade to version C.1.6 or later
  5. For AsteriskNOW: Upgrade to version 1.0.2 or later
  6. For s800i: Upgrade to version 1.1.0.2 or later
  7. For Asterisk Appliance Developer Kit: Upgrade to revision 104704 or later
  8. After upgrade, verify the manager ID generation uses proper randomization
Caveat Review release notes for backward compatibility with existing dialplan and configurations before upgrading major versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Asterisk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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