Endian FirewallApplication

CVE-2015-5082

HIGH · 10.0 CVSS v2.0 Published 2015-09-28
Fix available
A fix is available. Upgrade to after 2.5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit 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
Endian Firewall before 3.0 allows remote attackers to execute arbitrary commands via shell metacharacters in the (1) NEW_PASSWORD_1 or (2) NEW_PASSWORD_2 parameter to cgi-bin/chpasswd.cgi.

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

Endian Firewall before version 3.0 contains a command injection vulnerability in the chpasswd.cgi web script. The NEW_PASSWORD_1 and NEW_PASSWORD_2 parameters are not properly sanitized, allowing attackers to inject shell metacharacters and execute arbitrary OS commands remotely without authentication.

MitigationUpgrade to Endian Firewall 3.0 or later to obtain the patched version. If immediate patching is not feasible, restrict network access to the affected CGI interface via firewall rules or disable the password change functionality until upgrade can be completed.

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
Endian FirewallApplication
Affected:<= 2.5.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
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. Confirm Endian Firewall installation
    Check for Endian Firewall by reviewing system identification files, running 'cat /etc/redhat-release' or 'cat /etc/issue', or checking for /var/log/efw directory structure commonly found on Endian systems
    Affected if The system is not identified as an Endian Firewall installation
  2. Identify installed Endian Firewall version
    Run 'rpm -q endian-firewall' or check version files in /usr/lib/efw/ directory, or access the web interface and check the system information page
    Affected if The installed version is 2.5.1 or any version <= 2.5.1
  3. Locate the chpasswd.cgi script
    Search for the presence of chpasswd.cgi in the web root directories, typically found in /var/www/cgi-bin/ or /usr/local/httpd/cgi-bin/ on Endian systems
    Affected if The chpasswd.cgi script exists on the system in the expected CGI directories
  4. Verify password change interface is accessible
    Attempt to access the chpasswd.cgi via HTTP/HTTPS (e.g., GET request to the CGI endpoint) or check if the web service is running and the CGI module is enabled
    Affected if The web interface and chpasswd.cgi script are accessible over the network

A system is affected if it is running Endian Firewall version 2.5.1 or lower with the chpasswd.cgi web script accessible, allowing remote command injection through the NEW_PASSWORD parameters.

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.5.1
Interim mitigation

Upgrade to Endian Firewall 3.0 or later to obtain the patched version. If immediate patching is not feasible, restrict network access to the affected CGI interface via firewall rules or disable the password change functionality until upgrade can be completed.

Recommended fix High confidence

Endian Firewall 3.0 or later

  1. Download Endian Firewall version 3.0 or later from the official Endian network
  2. Back up all current configuration and data
  3. Perform a fresh installation or follow Endian's documented upgrade procedure to version 3.0
  4. Verify the upgrade was successful and the chpasswd.cgi interface functions correctly
  5. Test that the NEW_PASSWORD_1 and NEW_PASSWORD_2 parameters no longer accept shell metacharacters
Caveat Major version upgrade may require configuration migration; review Endian 3.0 migration documentation

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

Fix this in Endian Firewall Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-5082 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2015-5082 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