dbcve.org
Ingate FirewallHardware / appliance · Ingate

CVE-2007-6099

HIGH · 10.0 CVSS v2.0 Published 2007-11-22
Fix available
A fix is available. Upgrade to after 4.5.2 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
Unspecified vulnerability in Ingate Firewall before 4.6.0 and SIParator before 4.6.0 might leave "media pinholes" open upon a restart of the SIP module, which might make it easier for remote attackers to conduct unauthorized activities.

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

This is a vulnerability in Ingate Firewall and SIParator products where 'media pinholes' (temporary openings in the firewall for SIP media traffic) remain open after the SIP module restarts. Media pinholes should close when the SIP session ends or the module restarts; leaving them open allows unauthorized media traffic to bypass the firewall, potentially enabling remote attackers to conduct unauthorized activities through these persistent openings.

MitigationUpgrade Ingate Firewall and SIParator to version 4.6.0 or later, which addresses the improper handling of media pinholes upon SIP module restart. If upgrading is not immediately possible, consider network segmentation to limit exposure of the SIP-enabled interfaces.

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
Ingate FirewallHardware / appliance
Affected:<= 4.5.2
Ingate SiparatorHardware / appliance
Affected:<= 4.5.2

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. Identify the installed Ingate product
    Determine whether the system is running Ingate Firewall or Ingate SIParator. This is typically visible in the product name displayed in the web UI, CLI banner, or system documentation.
    Affected if The product is Ingate Firewall or SIParator and the version is unknown or <= 4.5.2
  2. Check the firmware/software version
    Locate the version number in the product's web interface (usually under System > Status or Help > About), CLI output (such as 'show version' or 'version' command), or system information page.
    Affected if The installed version is 4.5.2 or any earlier version (e.g., 4.5.1, 4.5.0, etc.)
  3. Verify SIP module is enabled
    Check the firewall configuration for active SIP signaling settings. In the web UI, look under VoIP/SIP settings, Firewall > VoIP, or similar SIP-related configuration sections. Confirm that SIP proxy or SIP gateway functionality is turned on.
    Affected if SIP module is enabled and configured to handle SIP traffic
  4. Inspect media pinhole behavior after SIP restart
    Observe the state of media pinholes (sometimes visible in firewall connection tables, NAT mappings, or VoIP-specific logs) before and after restarting the SIP module or after a SIP session ends. Look for connections that should timeout but remain active.
    Affected if Media pinholes persist in an open state after the SIP module restarts or after SIP sessions terminate, showing as active connections when they should be closed

The environment is affected if running Ingate Firewall or SIParator version 4.5.2 or earlier with SIP enabled, and media pinholes remain open after the SIP module restarts.

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 4.5.2
Interim mitigation

Upgrade Ingate Firewall and SIParator to version 4.6.0 or later, which addresses the improper handling of media pinholes upon SIP module restart. If upgrading is not immediately possible, consider network segmentation to limit exposure of the SIP-enabled interfaces.

Recommended fix High confidence

Ingate Firewall 4.6.0 or later / SIParator 4.6.0 or later

  1. 1. Back up the current Ingate Firewall/SIParator configuration before proceeding with any upgrade
  2. 2. Obtain the fixed version (4.6.0 or later) from the official Ingate website or authorized distribution channel
  3. 3. Review the upgrade documentation provided by Ingate for the 4.6.0 release
  4. 4. Apply the upgrade to the Ingate Firewall or SIParator device following the vendor's recommended upgrade procedure
  5. 5. After upgrade completion, verify that the SIP module restarts correctly and media pinholes are properly managed
  6. 6. Test SIP functionality to confirm normal operation

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

Fix this in Ingate Firewall Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,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 $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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