CVE-2013-4785
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 · uneditedThe web interface on the Dell iDRAC6 with firmware before 1.95 allows remote attackers to modify the CLP interface for arbitrary users and possibly have other impact via a request to an unspecified form that is accessible from testurls.html. NOTE: the vendor disputes the significance of this issue, stating "DRAC's are intended to be on a separate management network; they are not designed nor intended to be placed on or connected to the Internet."
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 confidenceThe Dell iDRAC6 web interface before firmware version 1.95 contains a vulnerability allowing remote attackers to modify the CLP (Common Line Interface) interface for arbitrary users via an unspecified form accessible from testurls.html. This allows unauthorized modification of user interface settings and potentially further compromise.
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= 1.7CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 iDRAC6 firmware versionAccess the iDRAC6 web interface and navigate to the Overview or About section, or use racadm command: racadm get idrac.infoAffected if Firmware version is 1.7 or any version below 1.95
-
Confirm iDRAC6 web interface is enabledCheck if the iDRAC web interface is accessible by attempting to reach https://<idrac-ip> in a browser, or verify via racadm: racadm get iDRAC.WebServer.1.WebServer.1Affected if Web interface is enabled and accessible on the network
-
Locate the vulnerable testurls.html pageAttempt to access the testurls.html page via the web interface at https://<idrac-ip>/testurls.htmlAffected if The page is accessible and responds without authentication
You are affected if your iDRAC6 firmware version is 1.7 or any version below 1.95 AND the iDRAC web interface is enabled and accessible.
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 · scopedUpdate iDRAC6 firmware to version 1.95 or later. Additionally, isolate the iDRAC interface on a dedicated management network separate from production traffic, as recommended by Dell's guidance.
iDRAC6 firmware version 1.95 or later
- 1. Download the iDRAC6 firmware version 1.95 or later from Dell's support website (support.dell.com)
- 2. Access the iDRAC6 web interface as an administrator
- 3. Navigate to the Firmware Update section (typically under 'Maintenance' or 'iDRAC Settings')
- 4. Upload the firmware file and initiate the update
- 5. Wait for the firmware update to complete and for the iDRAC6 to reboot
- 6. Verify the firmware version has been updated to 1.95 or later by checking the iDRAC6 web interface under 'iDRAC Settings' > 'General' > 'Firmware Version'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4785 — 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-2013-4785 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