CVE-2025-57846
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 · uneditedMultiple i-フィルター products contain an issue with incorrect default permissions. If this vulnerability is exploited, a local authenticated attacker may replace a service executable on the system where the product is running, potentially allowing arbitrary code execution with SYSTEM privileges.
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 confidenceMultiple i-フィルター products have incorrect default permissions on service executables, allowing a local authenticated attacker to replace the service binary and execute arbitrary code with SYSTEM privileges.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/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.
-
Identify i-フィルター services running on the systemOpen Services console (services.msc) or run 'sc queryex type= service state= all' to list all services. Look for service names containing 'i-フィルター', 'ifilter', or 'InterSAFE' (the product may be marketed under different names).Affected if Any i-フィルター service is found running on the system
-
Locate the service executable pathsFor each identified i-フィルター service, run 'sc qc <service_name>' to query the service configuration. The BINPATH field shows the executable path.Affected if The BINPATH points to an executable in a world-writable directory or with weak permissions
-
Check file permissions on service executablesRight-click each service executable, go to Properties > Security, or run 'icacls "<executable_path>"' from an elevated command prompt. Examine the permissions listed for Users and Authenticated Users.Affected if Users or Authenticated Users have Write or Write+Execute permissions on the service executable
-
Verify service runs with elevated privilegesRun 'sc qc <service_name>' and check the START_TYPE and RUNNING_AS fields. Also check in Services console whether the service runs as SYSTEM, Local System, or similar elevated account.Affected if The service runs as SYSTEM, Local System, or other elevated account and the executable is modifiable by low-privileged users
-
Test for unauthorized modification abilityFrom a standard user account (non-admin), attempt to create a test file in the service executable directory, or check if you can copy/overwrite the executable. Run 'icacls "<directory>"' as a standard user to see if they have modify rights.Affected if Standard users can modify files in the service executable directory or replace the binary itself
The system is affected if an i-フィルター service executable is writable by non-privileged users and runs with SYSTEM-level privileges, allowing potential local privilege escalation.
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 dataCorrect file system permissions on service executables to prevent modification by non-privileged users, and ensure service binaries are owned by TrustedInstaller or SYSTEM with restricted write access.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-57846 — 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-57846 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