CVE-2024-28810
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 · uneditedAn issue was discovered in Infinera hiT 7300 5.60.50. Sensitive information inside diagnostic files (exported by the @CT application) allows an attacker to achieve loss of confidentiality by analyzing these files.
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 confidenceThe Infinera hiT 7300 optical transport platform version 5.60.50 exports diagnostic files through the @CT application that contain sensitive information. An attacker with access to these exported diagnostic files can analyze them to extract confidential data, resulting in loss of confidentiality.
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= 5.60.50CVSS 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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:H/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 the device modelLog into the device management interface or check system information to confirm the hardware is a Nokia (formerly Infinera) hiT 7300 optical transport platformAffected if Device is not a hiT 7300 platform - not affected by this specific CVE
-
Check firmware versionAccess the device management console or system status page and locate the firmware version. On the hiT 7300, this is typically shown in the software version or system information section of the @CT or element manager interfaceAffected if Firmware version is not exactly 5.60.50 - not affected by this CVE
-
Verify @CT application accessAttempt to access the @CT application on the device. This is typically accessed via the management interface at a path such as /@CT or through the element manager applicationAffected if @CT application is not installed or not accessible - the vulnerability cannot be exploited
-
Check diagnostic export functionalityWithin the @CT application, navigate to the diagnostic export or file dump feature. Look for options to export system diagnostics, logs, or support filesAffected if Diagnostic export feature is not available or disabled - may reduce exposure but does not definitively rule out the vulnerability if other diagnostic paths exist
-
Inspect exported diagnostic contentIf you can legitimately export a diagnostic file, examine its contents for sensitive information such as credentials, configuration secrets, or private keys that should not be exposedAffected if Diagnostic files contain confidential data that should not be publicly accessible - confirms the vulnerability is present
A system is affected only if it is a Nokia hiT 7300 platform running exactly firmware version 5.60.50 with the @CT application accessible and diagnostic export functionality enabled, where exported files contain sensitive information.
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 dataRestrict access to diagnostic file exports from the @CT application, sanitize or remove sensitive information from diagnostic outputs, and apply any vendor-supplied patches for this issue.
- 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-2024-28810 — 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-2024-28810 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