CVE-2025-41667
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 · uneditedA low privileged remote attacker with file access can replace a critical file used by the arp-preinit script to get read, write and execute access to any file on the device.
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 confidenceA low-privilege attacker with file access can replace a critical file used by the arp-preinit script on a network device, enabling read, write, and execute access to arbitrary files on the device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Locate the arp-preinit scriptSearch for the arp-preinit file on the system using: find / -name 'arp-preinit' 2>/dev/null or ls -la /etc/init.d/arp-preinitAffected if The script exists on the device - vulnerability applies if found
-
Check file permissions on arp-preinitRun ls -la on the found arp-preinit script path to view owner, group, and permission bitsAffected if Permissions allow write access for non-root users (e.g., world-writable or group-writable with weak group membership)
-
Identify the critical file the script usesExamine the script contents with cat <path_to_arp-preinit> and look for file paths it references or sourcesAffected if The script references a configurable file path that could be replaced by a low-privilege attacker
-
Check parent directory permissionsList permissions on the directory containing the arp-preinit script: ls -ld /etc/init.d/ or the parent directory found in step 1Affected if The directory is world-writable or allows non-privileged users to create/modify files
-
Verify script integrityCompare the current script against known-good backups, or check file hashes if available, or review the script for unexpected file operationsAffected if The script references a file that an attacker could replace to gain arbitrary file read/write/execute access
The device is affected if an arp-preinit script exists and either the script itself or the directory containing it has weak permissions allowing a low-privilege attacker to replace critical files it references.
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 file system permissions to prevent unauthorized modification of critical scripts like arp-preinit, and implement integrity verification mechanisms for initialization scripts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41667 — 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-2025-41667 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