dbcve.org
AsteriskApplication · Sangoma

CVE-2024-35190

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-17
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
62/100
Remediation priority · Elevated
Public exploit Remotely reachable No privileges Zero-click Patch available

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
Asterisk is an open source private branch exchange and telephony toolkit. After upgrade to 18.23.0, ALL unauthorized SIP requests are identified as PJSIP Endpoint of local asterisk server. This vulnerability is fixed in 18.23.1, 20.8.1, and 21.3.1.

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

A detailed technical summary for this CVE is being prepared.

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:= 18.23.0= 20.8.0= 21.3.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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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
Patch available Apply the vendor patch
Vendor patch github.com →
Recommended fix High confidence

Asterisk 18.23.1, 20.8.1, or 21.3.1 (depending on your current branch)

  1. 1. Identify your current Asterisk version using 'asterisk -V' or 'core show version'
  2. 2. Determine which release branch you are on (18.x, 20.x, or 21.x)
  3. 3. Upgrade to the corresponding fixed release: 18.23.1 for branch 18.x, 20.8.1 for branch 20.x, or 21.3.1 for branch 21.x
  4. 4. For package-based installations, use your distribution's package manager (e.g., apt-get install asterisk, yum update asterisk, or dnf update asterisk)
  5. 5. For source installations, download the appropriate source tarball from https://downloads.asterisk.org/pub/telephony/asterisk/ and rebuild
  6. 6. After upgrade, restart the Asterisk service (e.g., 'systemctl restart asterisk' or 'asterisk -rx core restart gracefully')
  7. 7. Verify the fix by testing SIP authentication - unauthorized requests should no longer be misidentified as local endpoints

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

We can apply and verify the patch for your build — typical engagement from $1,600. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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