Hit 7300 FirmwareOperating system · Nokia

CVE-2024-28812

HIGH · 8.8 CVSS v3.1 Published 2024-09-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

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 · unedited
An issue was discovered in Infinera hiT 7300 5.60.50. A hidden SSH service (on the local management network interface) with hardcoded credentials allows attackers to access the appliance operating system (with highest privileges) via an SSH connection.

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 confidence

The Infinera hiT 7300 optical transport platform version 5.60.50 contains a hidden SSH service listening on the local management network interface. This service uses hardcoded credentials, allowing any attacker with network access to the management interface to bypass authentication and gain root-level command execution on the appliance operating system.

MitigationApply vendor-provided firmware patch to remove the hidden SSH service and hardcoded credentials; as interim control, restrict management interface access via network segmentation or ACLs to prevent unauthorized access.

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
Hit 7300 FirmwareOperating system
Affected:= 5.60.50

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model and firmware version
    Access the hiT 7300 management interface or use SNMP/WEB to retrieve the firmware version information. Typically found in System > Software or Version status screens.
    Affected if The firmware version is exactly 5.60.50.
  2. Check for SSH services on non-standard ports
    Perform a port scan (e.g., nmap) against the management interface IP address, scanning common and non-standard SSH ports (22, 2222, 22222, 8022, etc.). Use command: nmap -p 22,2222,22222,8022,10022 -sV <management_ip>
    Affected if An SSH service is detected on any port besides the standard port 22, indicating a hidden service may be running.
  3. Verify SSH service responds on local management interface
    Attempt to connect to potential hidden SSH ports found in step 2. Use: ssh -p <port> <user>@<management_ip> with any username to test if authentication is bypassed.
    Affected if The SSH connection succeeds without valid credentials or immediately accepts authentication, indicating hardcoded credentials are in use.
  4. Check network accessibility of management interface
    Review network configuration to determine if the management interface is accessible from untrusted networks. Check VLAN assignment, ACLs, and interface binding.
    Affected if The management interface is bound to a network segment accessible from non-management networks, allowing external attackers to reach the hidden service.

A system is affected if it is an Infinera/Nokia hiT 7300 running firmware version 5.60.50 with an accessible SSH service on the management interface that accepts unauthenticated connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided firmware patch to remove the hidden SSH service and hardcoded credentials; as interim control, restrict management interface access via network segmentation or ACLs to prevent unauthorized access.

Fix this in Hit 7300 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28812 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-28812 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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