dbcve.org
IcingaApplication

CVE-2013-7106

MEDIUM · 6.5 CVSS v2.0 Published 2014-01-15
Fix available
A fix is available. Upgrade to after 1.8.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 stack-based buffer overflows in Icinga before 1.8.5, 1.9 before 1.9.4, and 1.10 before 1.10.2 allow remote authenticated users to cause a denial of service (crash) and possibly execute arbitrary code via a long string to the (1) display_nav_table, (2) page_limit_selector, (3) print_export_link, or (4) page_num_selector function in cgi/cgiutils.c; (5) status_page_num_selector function in cgi/status.c; or (6) display_command_expansion function in cgi/config.c. NOTE: this can be exploited without authentication by leveraging CVE-2013-7107.

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

Stack-based buffer overflows in Icinga's CGI components (cgiutils.c, status.c, config.c) allow remote authenticated users to crash the service or execute arbitrary code via overly long strings passed to functions like display_nav_table, page_limit_selector, print_export_link, page_num_selector, status_page_num_selector, and display_command_expansion. The vulnerable functions do not properly validate input string length before copying to fixed-size stack buffers.

MitigationUpgrade Icinga to version 1.8.5, 1.9.4, or 1.10.2 or later. As a temporary workaround, restrict CGI access and implement input length validation on the affected endpoints.

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
IcingaApplication
Affected:<= 1.8.4= 0.8.0= 0.8.1= 0.8.2= 0.8.3= 0.8.4= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.2.0= 1.2.1

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
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/I:P/A:P

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. Confirm Icinga is installed
    Check for Icinga installation directories such as /usr/local/icinga, /opt/icinga, or use package management commands like 'rpm -qa | grep icinga' or 'dpkg -l | grep icinga'
    Affected if Icinga is not installed or the installation cannot be determined
  2. Determine installed Icinga version
    Run 'icinga --version' or 'icinga -V', or check version files in the installation directory such as VERSION, or query the package manager for the installed version
    Affected if The installed version is 1.8.4 or lower, or matches any of these specific versions: 0.8.0, 0.8.1, 0.8.2, 0.8.3, 0.8.4, 1.0, 1.0.1, 1.0.2, 1.0.3, 1.2.0, 1.2.1
  3. Verify CGI module is enabled and accessible
    Check the web server configuration for CGI script execution related to Icinga, typically in Apache config files under /etc/httpd/conf.d/ or /etc/apache2/sites-available/, looking for cgi-bin or icinga/cgi-bin paths
    Affected if CGI scripts for Icinga are enabled and accessible via the web server
  4. Confirm remote authentication is permitted
    Review web server access controls and Icinga authentication settings in icinga.cfg or cgi.cfg to determine if remote users can authenticate to access CGI endpoints
    Affected if Remote unauthenticated or authenticated users can reach the CGI interface

Your environment is affected if Icinga is installed with a version in the 0.8.x, 1.0.x, 1.2.x, or 1.8.x through 1.8.4 series AND the CGI interface is accessible to remote users.

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.

From vendor data
Upgrade available Upgrade to a release after 1.8.4
Interim mitigation

Upgrade Icinga to version 1.8.5, 1.9.4, or 1.10.2 or later. As a temporary workaround, restrict CGI access and implement input length validation on the affected endpoints.

Fix this in Icinga Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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