dbcve.org
Hit 7300 FirmwareOperating system · Nokia

CVE-2024-28813

HIGH · 8.4 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 →
86/100
Remediation priority · High
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. Undocumented privileged functions in the @CT management application allow an attacker to activate remote SSH access to the appliance via an unexpected network interface.

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 confidence

The Infinera hiT 7300 optical transport platform version 5.60.50 contains undocumented privileged functions within its @CT management application. These hidden functions can be exploited to enable remote SSH access through an undocumented or unexpected network interface, potentially granting attackers shell access to the appliance without authentication.

MitigationIsolate the device on a restricted network segment, contact Infinera for a firmware update that removes the undocumented functions, and implement network-level controls to monitor and block unauthorized SSH access on non-standard interfaces.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/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 firmware version
    Access the system CLI or web management interface and retrieve the firmware version. On the Nokia Hit 7300, this is typically shown via 'show version' command in CLI or displayed in the system information page of the web UI.
    Affected if The installed firmware version is exactly 5.60.50, as this is the only affected version listed.
  2. Confirm the @CT management application is present
    Check if the @CT application is installed or enabled on the device. This may be visible in the system menu under applications, or via CLI command such as 'show applications' or 'show running-config | include @CT' if available.
    Affected if The @CT management application is installed and running on the device.
  3. Inspect SSH service configuration
    Review the SSH service configuration to determine which network interfaces it is bound to. Use commands like 'show ssh server' or 'show services' in the device CLI to list all interfaces where SSH is enabled.
    Affected if SSH is enabled on any interface other than the expected primary management interface, or on an unexpected interface.
  4. Check for undocumented or secondary network interfaces
    List all network interfaces on the device using commands like 'show ip interface' or 'show interfaces' to identify all IP addresses and interfaces configured on the system.
    Affected if There are network interfaces present that are not part of the documented or expected management network topology.
  5. Verify SSH access controls
    Review access control lists or firewall rules that govern SSH access. Check if there are any rules allowing SSH from untrusted or unexpected source networks.
    Affected if SSH access is permitted from networks other than the designated trusted management network.

A system is affected if it is running firmware version 5.60.50 on a Nokia Hit 7300 or Infinera hiT 7300 platform, the @CT management application is present, and SSH is accessible via any interface beyond the intended management network.

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

Isolate the device on a restricted network segment, contact Infinera for a firmware update that removes the undocumented functions, and implement network-level controls to monitor and block unauthorized SSH access on non-standard interfaces.

Fix this in Hit 7300 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28813 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-28813 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