CVE-2025-0224
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 vulnerability was found in Provision-ISR SH-4050A-2, SH-4100A-2L(MM), SH-8100A-2L(MM), SH-16200A-2(1U), SH-16200A-5(1U) and NVR5-8200PX up to 20241220. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file /server.js. The manipulation leads to information disclosure. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.
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 confidenceAn information disclosure vulnerability exists in the /server.js file of multiple Provision-ISR NVR models (SH-4050A-2, SH-4100A-2L, SH-8100A-2L, SH-16200A-2/5, NVR5-8200PX) allowing remote attackers to access sensitive information. The exploit has been publicly disclosed, increasing exploitation risk.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the NVR modelAccess the device web interface or check the device label/documentation to confirm the exact model number (SH-4050A-2, SH-4100A-2L, SH-8100A-2L, SH-16200A-2/5, or NVR5-8200PX)Affected if The model number matches one of the affected models listed in the CVE
-
Verify the web server is runningAttempt to access the device login page or /server.js endpoint over HTTP/HTTPS (e.g., http://<device-ip>/server.js) using curl or a web browserAffected if The device responds with content, indicating the web server is active and potentially exposing the vulnerable endpoint
-
Check for information disclosure in /server.jsInspect the response from accessing /server.js - look for hardcoded credentials, API keys, internal paths, or configuration details that should not be publicly visibleAffected if The /server.js file returns sensitive information such as credentials, internal network details, or configuration data
-
Assess network exposureDetermine if the NVR device is directly accessible from the internet (public IP) or behind a proper firewall. Check router/firewall port forwarding rules for the device's HTTP/HTTPS portsAffected if The device web interface is accessible from the internet without VPN or firewall restrictions
-
Confirm firmware versionLog into the device admin panel and navigate to System > About or System > Firmware to check the installed firmware version. Compare against any vendor release notesAffected if The firmware version cannot be confirmed as patched or is older than the latest available version from Provision-ISR
A user is affected if they own one of the listed NVR models with the web interface accessible (either locally or exposed) and the /server.js file returns sensitive information that should not be disclosed.
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 dataApply the latest vendor firmware update from Provision-ISR for affected NVR models. If no patch is available, isolate devices behind a firewall and disable unnecessary network exposure.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0224 — 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-0224 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