CVE-2020-24646
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 · uneditedA tftpserver stack-based buffer overflow remote code execution vulnerability was discovered in HPE Intelligent Management Center (iMC) version(s): Prior to iMC PLAT 7.3 (E0705P07).
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 confidenceA stack-based buffer overflow vulnerability in the tftpserver component of HPE Intelligent Management Center (iMC) allows remote attackers to execute arbitrary code via crafted TFTP requests. The vulnerability stems from insufficient bounds checking when processing TFTP packet data, enabling an attacker to overwrite stack memory and redirect execution flow.
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< 7.3= 7.3CVSS 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.
-
Verify HPE iMC is installedCheck system for HPE Intelligent Management Center installation - look for iMC installation directories (commonly in C:\hp\imc or C:\Program Files\HP\iMC) or check Windows Programs and Features for 'HP Intelligent Management Center'Affected if HPE iMC is not installed on the system
-
Determine installed iMC versionCheck the iMC version - typically found in the PLAT\app\version.ini file or via the iMC management console under Help > About. Compare the version number against the affected ranges: versions less than 7.3 or exactly version 7.3Affected if Installed version is less than 7.3 or equals 7.3
-
Check if tftpserver component is enabledExamine the tftpserver service status - in Windows this appears as a service named 'tftpserver' or part of the iMC service bundle. Use 'services.msc' or command 'sc query tftpserver' to check if the service exists and is runningAffected if The tftpserver service exists and is running
-
Verify TFTP port is listeningCheck if UDP port 69 (the standard TFTP port) is open and listening on the iMC server. Use command 'netstat -an | findstr :69' or a port scanner. The presence of a listening UDP port indicates the TFTP server is activeAffected if UDP port 69 is open and listening on the affected system
A system is affected if HPE Intelligent Management Center is installed with version 7.3 or any version below 7.3 AND the tftpserver component is enabled with TFTP port 69 listening.
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.3
Upgrade to HPE iMC PLAT 7.3 (E0705P07) or later. As a compensating control, restrict network access to the TFTP server port and disable the tftpserver service if not required.
iMC PLAT 7.3 (E0705P07)
- Upgrade HPE Intelligent Management Center to iMC PLAT 7.3 (E0705P07) or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24646 — 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-2020-24646 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