CVE-2025-27023
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 · uneditedLack or insufficent input validation in WebGUI CLI web in Infinera G42 version R6.1.3 allows remote authenticated users to read all OS files via crafted CLI commands. Details: The web interface based management of the Infinera G42 appliance enables the feature of executing a restricted set of commands. This feature also offers the option to execute a script-file already present on the target device. When a non-script or incorrect file is specified, the content of the file is shown along with an error message. Due to an execution of the http service with a privileged user all files on the file system can be viewed this way.
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 confidenceInfinera G42 R6.1.3 contains an arbitrary file read vulnerability in the WebGUI CLI feature. The script-file execution function does not validate input properly, and when a non-script or incorrect filename is provided, the file content is returned with an error message. Because the http service runs with privileged user context, any authenticated user can read arbitrary OS files by specifying the full path in this parameter.
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>= 6.1.3, < 7.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Check firmware versionAccess the device admin interface or use CLI command 'show version' to retrieve the installed firmware versionAffected if Version is greater than or equal to 6.1.3 and less than 7.1
-
Verify WebGUI CLI accessLog into the WebGUI and navigate to the CLI feature section, or check if the CLI web interface endpoint is accessible to authenticated usersAffected if WebGUI CLI feature is enabled and accessible to non-privileged users
-
Confirm service privilege contextCheck the http service configuration to determine if it runs with privileged (root/administrator) user context rather than a limited service accountAffected if HTTP service runs with elevated/privileged user privileges
-
Test arbitrary file read (if authorized)Using an authenticated user session, attempt to access the script-file execution function with an absolute file path such as /etc/passwd as the filename parameterAffected if File content is returned or accessible without proper validation
The environment is affected if the firmware version falls within 6.1.3 to 7.0.x range AND the WebGUI CLI feature is accessible to authenticated users running with elevated privileges.
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.
dbcve · scoped7.1
Apply vendor patch when available. Until then, restrict user access to the CLI web interface, implement input validation on the script filename parameter, and ensure the http service runs with least-privilege user context rather than elevated privileges.
G42 firmware version 7.1 or later
- Contact Infinera support or access the official Infinera support portal to obtain the G42 firmware upgrade
- Download G42 firmware version 7.1 or later
- Review Infinera's official firmware upgrade documentation for G42 devices
- Execute the firmware upgrade following Infinera's standard upgrade procedure
- Verify the upgrade completed successfully and confirm the device is running version 7.1 or later
- Test that the WebGUI CLI functionality works correctly with the new firmware
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2025-27023 — 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-27023 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