dbcve.org
EkigaApplication

CVE-2007-1006

HIGH · 10.0 CVSS v2.0 Published 2007-02-20
Fix available
A fix is available. Upgrade to after 2.0.4 or later.
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
Multiple format string vulnerabilities in the gm_main_window_flash_message function in Ekiga before 2.0.5 allow attackers to cause a denial of service and possibly execute arbitrary code via a crafted Q.931 SETUP 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 confidence

Format string vulnerability in Ekiga's gm_main_window_flash_message function allows remote attackers to execute arbitrary code or cause denial of service via crafted Q.931 SETUP packets used in H.323 VoIP protocol. The vulnerability stems from user-supplied data being passed as a format string without proper sanitization.

MitigationUpgrade Ekiga to version 2.0.5 or later to address the format string vulnerability. If upgrading is not feasible, consider disabling H.323 protocol support or implementing network-level filtering of untrusted Q.931 packets.

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
EkigaApplication
Affected:<= 2.0.4

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
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 checks

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

  1. Verify Ekiga is installed
    Check for the presence of the Ekiga executable. On Linux, run 'which ekiga' or look for /usr/bin/ekiga. On Windows, check Program Files for Ekiga folder.
    Affected if Ekiga executable exists on the system
  2. Determine installed Ekiga version
    Run 'ekiga --version' or 'ekiga -v' from the command line to retrieve the exact version number.
    Affected if The version returned is 2.0.4 or lower
  3. Confirm H.323 protocol support is enabled
    Open Ekiga and navigate to Edit > Preferences > Protocol Settings, or inspect Ekiga's configuration files (typically ~/.gconf/apps/ekiga/ or ~/.config/ekiga/) for H.323-related settings.
    Affected if H.323 protocol support is turned on in the application settings
  4. Check if H.323 listener is active
    Run 'netstat -an | grep 1720' or 'ss -an | grep 1720' to see if Ekiga is listening on the default H.323 port 1720.
    Affected if The system is listening on port 1720 for incoming H.323 connections

The system is affected if Ekiga version 2.0.4 or lower is installed with H.323 protocol support enabled and potentially listening for connections.

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
Upgrade available Upgrade to a release after 2.0.4
Interim mitigation

Upgrade Ekiga to version 2.0.5 or later to address the format string vulnerability. If upgrading is not feasible, consider disabling H.323 protocol support or implementing network-level filtering of untrusted Q.931 packets.

Recommended fix High confidence

Ekiga 2.0.5 or later

  1. 1. Check the current installed version of Ekiga by running 'ekiga --version' or checking your package manager
  2. 2. Remove the vulnerable Ekiga 2.0.4 installation using your system's package manager (e.g., 'yum remove ekiga' or 'dnf remove ekiga' on Fedora/RHEL, 'apt-get remove ekiga' on Debian/Ubuntu)
  3. 3. Update your package repository lists to ensure you have access to the latest packages
  4. 4. Install Ekiga version 2.0.5 or later from your distribution's package repository (e.g., 'yum install ekiga' or 'dnf install ekiga' on Fedora/RHEL, 'apt-get install ekiga' on Debian/Ubuntu)
  5. 5. Verify the new version is installed by running 'ekiga --version'
  6. 6. Restart any running Ekiga instances and test that the application functions normally

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

Fix this in Ekiga Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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