CVE-2009-3447
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 · uneditedUnrestricted file upload vulnerability in RADactive I-Load before 2008.2.5.0 allows remote attackers to execute arbitrary code by uploading a file with an executable extension, and then sending a request for a predictable filename during a short time window.
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 confidenceRADactive I-Load before version 2008.2.5.0 suffers from an unrestricted file upload vulnerability allowing remote attackers to upload files with executable extensions (e.g., .asp, .php, .exe). Combined with a predictable filename generation mechanism and a narrow exploitation time window, attackers can subsequently request the uploaded malicious file to achieve arbitrary 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<= 2008.2.4.0= 1.6.3= 1.6.3.1= 1.6.3.2= 1.6.3.3= 1.7.0.0= 1.7.0.1= 1.7.0.2= 1.7.0.3= 1.7.0.4= 1.7.0.5= 1.7.0.6CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
-
Locate RADactive I-Load installationSearch for RADactive I-Load components on the web server, typically found in the web application's /bin directory or within the application's root folder. Check for files named i-load.dll, iload.dll, or similar RADactive components.Affected if The software is present on the server and serves web requests.
-
Identify installed versionRight-click the RADactive I-Load DLL file, select Properties, and view the Version tab. Alternatively, check the version information in the application itself or any version.txt/readme file distributed with the software.Affected if The version number matches any of the affected versions: 1.6.3, 1.6.3.1, 1.6.3.2, 1.6.3.3, 1.7.0.0 through 1.7.0.6, or is 2008.2.4.0 or lower.
-
Confirm upload functionality is enabledAccess the I-Load administrative interface or test the upload endpoint if known. Check the application's configuration files (such as web.config or i-load.config) for upload-related settings.Affected if The upload module is accessible and not disabled in configuration.
-
Inspect file type restrictionsExamine the application configuration or source code for allowed file extensions. Look for settings that permit .asp, .php, .exe, or other executable extensions in upload filters.Affected if Executable file extensions are permitted in upload settings or no extension filtering is configured.
A system is affected if RADactive I-Load is installed with a version between 1.6.3 and 1.7.0.6 inclusive, or 2008.2.4.0 or lower, and the upload feature is accessible without proper file type restrictions.
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 dataUpgrade to RADactive I-Load version 2008.2.5.0 or later, which implements proper filename randomization and restricts executable file type uploads. If upgrading is not immediately feasible, disable the upload functionality or implement web application firewall rules to block executable file extensions.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-3447 — 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-2009-3447 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