CVE-2025-27019
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 · uneditedRemote shell service (RSH) in Infinera MTC-9 version R22.1.1.0275 allows an attacker to utilize password-less user accounts and obtain system access by activating a reverse shell.This issue affects MTC-9: from R22.1.1.0275 before R23.0.
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 · high confidenceThe Infinera MTC-9 RSH (Remote Shell) service contains hardcoded or password-less user accounts that allow unauthenticated attackers to execute commands on the device. By activating a reverse shell through these accounts, attackers can gain full system access without credentials.
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>= 22.1.1.0275, < 23.0CVSS 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.
-
Identify firmware versionAccess device CLI or web management interface and retrieve the current firmware version informationAffected if Installed version is >= 22.1.1.0275 and < 23.0 (any 22.x.x version in this range)
-
Confirm RSH service is enabledCheck device configuration or running services to determine if the Remote Shell (RSH) service is activeAffected if RSH service is enabled or running on the device
-
Verify RSH port accessibilityScan network ports or review firewall rules to check if port 514 (RSH default) is open and reachableAffected if Port 514 is accessible from network segments that are not trusted or are externally facing
-
Review RSH user accountsExamine device configuration for user accounts configured with RSH access permissionsAffected if Any RSH-specific user accounts exist without proper authentication requirements
Device is affected if firmware version is within 22.1.1.0275 to 22.x and the RSH service is enabled and accessible on the network
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 · scoped23.0
Upgrade Infinera MTC-9 firmware to R23.0 or later. If RSH is not required, disable the service. Restrict network access to RSH ports (typically 514) using firewalls or ACLs to prevent external exploitation.
R23.0 or later
- 1. Access the Infinera MTC-9 device administration interface or console.
- 2. Verify the current firmware version is between R22.1.1.0275 and R23.0 (exclusive).
- 3. Download the official R23.0 firmware update from Infinera's authorized support channels.
- 4. Create a backup of the current device configuration before proceeding.
- 5. Initiate the firmware upgrade process following Infinera's standard upgrade procedure.
- 6. Verify the upgrade completed successfully and the device is running R23.0 or later.
- 7. Confirm the RSH service is no longer accessible without authentication.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27019 — 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-27019 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