CVE-2024-9132
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 · uneditedThe administrator is able to configure an insecure captive portal script
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 · moderate confidenceThis is a vulnerability in captive portal functionality where an administrator can configure an insecure script, potentially leading to remote code execution or system compromise. The critical CVSS score suggests the vulnerability is exploitable over the network without authentication and results in complete system compromise.
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<= 17.1.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check Arista Ng Firewall versionAccess the administration interface or run 'sfwver' or 'version' command in CLI to retrieve the installed firmware versionAffected if The installed version is 17.1.1 or lower
-
Verify captive portal statusNavigate to Captive Portal settings in the web interface or check configuration for 'captive-portal' or 'cp' related settings via CLI with 'config show' or equivalent commandAffected if Captive portal is enabled and active on the system
-
Inspect custom script configurationIn captive portal settings, examine any field that allows specifying a custom script path, often labeled as 'Custom Script', 'Redirect Script', or similar. Look for user-defined script paths in the configuration file typically found in /var/ipfire/captiveportal/ or similar pathsAffected if A custom script path is defined and points to a user-controlled or writable location
-
Review script file permissions and ownershipExamine the configured script file using 'ls -la <script_path>' to check if it is writable by non-privileged users or if it resides in a user-modifiable directoryAffected if The script file is writable by the web server process, low-privilege users, or resides outside system-controlled directories
A system is affected if it runs Arista Ng Firewall version 17.1.1 or lower with captive portal enabled and a custom script path configured that is writable or user-controlled.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict or disable the ability for administrators to configure custom captive portal scripts. Implement strict validation, sandboxing, or whitelisting for any script execution, and review existing configurations for insecure script paths.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-9132 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-9132 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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