dbcve.org
Debian LinuxOperating system · Debian

CVE-2013-4158

MEDIUM · 6.1 CVSS v3.1 Published 2019-12-11
Fix available
A fix is available. Upgrade to 2.6.9 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
smokeping before 2.6.9 has XSS (incomplete fix for CVE-2012-0790)

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

Smokeping before version 2.6.9 contains a cross-site scripting (XSS) vulnerability that represents an incomplete fix for CVE-2012-0790. The vulnerability allows attackers to inject malicious scripts through unsanitized input fields in the web interface.

MitigationUpgrade Smokeping to version 2.6.9 or later to obtain the complete fix for the XSS vulnerability.

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
Debian LinuxOperating system
Affected:= 8.0= 9.0= 10.0
FedoraOperating system
Affected:= 18= 19
SmokepingApplication
Affected:< 2.6.9

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Check if Smokeping is installed
    Run: dpkg -l | grep smokeping (Debian) or rpm -qa | grep smokeping (Fedora/RHEL)
    Affected if Smokeping package is found on the system
  2. Determine installed Smokeping version
    Run: dpkg -s smokeping (Debian) or rpm -qi smokeping (Fedora) and note the Version field
    Affected if Version is lower than 2.6.9 (for example, 2.6.8, 2.6.7, etc.)
  3. Verify web interface is enabled
    Check if Apache or other web server is configured with Smokeping CGI, or look for smokeping.fcgi or smokeping.cgi in web server directories (commonly /usr/lib/cgi-bin/ or /var/www/cgi-bin/)
    Affected if The Smokeping CGI web interface is present and accessible via HTTP/HTTPS
  4. Confirm the installation source
    If using Debian, check /etc/debian_version to confirm running version 8, 9, or 10; if using Fedora, confirm version 18 or 19
    Affected if Running Debian 8, 9, or 10, or Fedora 18 or 19, with Smokeping installed from system packages

You are affected if Smokeping is installed with a version lower than 2.6.9 and the web interface CGI is accessible, particularly on Debian 8/9/10 or Fedora 18/19 systems.

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 2.6.9 or later
Fixed in 2.6.9
Interim mitigation

Upgrade Smokeping to version 2.6.9 or later to obtain the complete fix for the XSS vulnerability.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
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,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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