CVE-2017-4990
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 · uneditedIn EMC Avamar Server Software 7.4.1-58, 7.4.0-242, 7.3.1-125, 7.3.0-233, 7.3.0-226, an unauthorized attacker may leverage the file upload feature of the system maintenance page to load a maliciously crafted file to any directory which could allow the attacker to execute arbitrary code on the Avamar Server system.
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 confidenceEMC Avamar Server contains an unauthenticated file upload vulnerability in its system maintenance page. An unauthenticated attacker can upload malicious files to arbitrary directories on the server, achieving remote code execution.
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.0-226= 7.3.0-233= 7.3.1-125= 7.4.0-242= 7.4.1-58CVSS 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.0/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.
-
Confirm the product is EMC Avamar ServerIdentify the installed product by checking the system banner, product name in the web interface, or running 'avamar' version commands if available on the system.Affected if The system is not EMC Avamar Server.
-
Determine the installed Avamar versionLocate the installed version number through the administrative web console, command-line interface, or system files. Common locations include the About page in the management interface or running 'avamar --version' if accessible.Affected if The installed version matches one of the following: 7.3.0-226, 7.3.0-233, 7.3.1-125, 7.4.0-242, or 7.4.1-58.
-
Identify if the system maintenance page is accessibleAttempt to access the maintenance page endpoint (typically found at /maint or similar paths under the web interface). Check if the page loads without requiring login credentials.Affected if The system maintenance page is reachable without authentication.
-
Verify network exposure of the maintenance interfaceReview firewall rules, network configurations, or ACLs to determine if the maintenance page is exposed to untrusted networks or the internet. Check if port 443 or the web interface port accepts external connections.Affected if The maintenance interface is accessible from untrusted networks.
The environment is affected if running any of the affected versions (7.3.0-226, 7.3.0-233, 7.3.1-125, 7.4.0-242, or 7.4.1-58) AND the system maintenance page is accessible without authentication.
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 dataApply vendor-supplied patches for affected versions. Until patching is feasible, disable or restrict access to the system maintenance page via network segmentation or firewall rules.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-4990 — 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-2017-4990 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