CVE-2007-4103: n/a vulnerability

CVE-2007-4103: The IAX2 channel driver (chan_iax2) in Asterisk Open 1.2.x before 1.2.23, 1.4.x before 1.4.9, and Asterisk...

The IAX2 channel driver (chan_iax2) in Asterisk Open 1.2.x before 1.2.23, 1.4.x before 1.4.9, and Asterisk Appliance Developer Kit before 0.6.0, when configured to allow unauthenticated calls, allows remote attackers to cause a denial of service (resource exhaustion) via a flood of calls that do not complete a 3-way handshake, which causes an ast_channel to be allocated but not released.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 14:46 UTC (UTC+00:00)

Security readout for executives and security teams

This vulnerability can let an unauthenticated remote caller exhaust resources on affected Asterisk systems using IAX2, potentially disrupting voice services. Exposure depends on a specific configuration: IAX2 must allow unauthenticated calls. Public sources identify fixed releases, but no CVSS score or active exploitation evidence is provided. Likely exposure is limited to legacy Asterisk deployments using affected versions with IAX2 configured to permit unauthenticated calls. Internet-facing VoIP gateways or PBX systems are the main concern. Systems not using IAX2, not allowing unauthenticated calls, or running fixed versions are less likely exposed. Prioritize if the organization still operates legacy Asterisk voice infrastructure, especially internet-facing IAX2 services. The business risk is service disruption, not confirmed compromise. For modern or non-IAX2 environments, treat this as a targeted legacy exposure check. Mitigation focus: Upgrade Asterisk Open 1.2.x to 1.2.23 or later where applicable.; Upgrade Asterisk Open 1.4.x to 1.4.9 or later where applicable.; Upgrade Asterisk Appliance Developer Kit to 0.6.0 or later where applicable..

Prepared: Jun 29, 2026, 04:20 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2007-4103 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jul 31, 2007, 10:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.