FortiosOperating system · Fortinet
CVE-2005-3057
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 FTP component in FortiGate 2.8 running FortiOS 2.8MR10 and v3beta, and other versions before 3.0 MR1, allows remote attackers to bypass the Fortinet FTP anti-virus engine by sending a STOR command and uploading a file before the FTP server response has been sent, as demonstrated using LFTP.
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 confidenceThis is a race condition (TOCTOU) vulnerability in FortiGate's FTP anti-virus scanning component. Attackers bypass the AV engine by sending a STOR command and uploading a malicious file before the FTP server can respond or initiate the scan, as demonstrated with LFTP. The vulnerability affects FortiOS 2.8MR10, v3beta, and versions before 3.0 MR1.
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
FortiosOperating system
<= 2.8_mr10<= 3_beta
FortigateHardware / appliance
= 2.8CVSS 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.
-
Determine the FortiOS versionLog into the FortiGate CLI and run `get system status` or `get system version` to retrieve the installed FortiOS version stringAffected if The displayed version is 2.8MR10 or lower, any 3.x beta version, or any version prior to 3.0 MR1 (such as 2.8MR7, 2.8MR9, 3.0alpha, 3.0beta)
-
Verify FTP anti-virus scanning is enabledIn the FortiGate web UI under Security Profiles > AntiVirus or via CLI with `get antivirus profile` or `show firewall profile`, check if an AV profile is assigned to FTP traffic inspectionAffected if FTP AV scanning is actively configured and applied to FTP traffic policies, creating the condition where the race can be exploited
Your FortiGate is affected if it runs FortiOS version 2.8MR10 or lower, any 3.x beta, or any version before 3.0 MR1 AND has FTP anti-virus scanning enabled in security policies.
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 · scopedUpgrade FortiGate devices to FortiOS 3.0 MR1 or later, which contains the fix for this race condition in the FTP anti-virus engine.
FortiOS 3.0 MR1 or later
- Access the FortiGate unit through the web-based manager or console
- Navigate to System > Firmware or use the 'execute upgrade' command
- Upload the FortiOS 3.0 MR1 or later firmware image
- Reboot the FortiGate unit to apply the new firmware
- Verify the firmware version after reboot using 'get system status' command
- Test FTP functionality to confirm the anti-virus engine is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortios
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3057 — 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-2005-3057 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