dbcve.org
F Secure Anti VirusApplication · F Secure

CVE-2007-3300

HIGH · 9.3 CVSS v2.0 Published 2007-06-20
Fix available
A fix is available. Upgrade to after 6.61 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Multiple F-Secure anti-virus products for Microsoft Windows and Linux before 20070619 allow remote attackers to bypass scanning via a crafted header in a (1) LHA or (2) RAR archive.

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 confidence

F-Secure anti-virus products for Windows and Linux versions before June 19, 2007 contain a vulnerability where specially crafted headers in LHA or RAR archive files can bypass the antivirus scanning engine, allowing malicious payloads to be delivered without detection.

MitigationUpdate F-Secure anti-virus products to versions released after June 19, 2007 to patch the scanning bypass vulnerability.

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
F Secure Anti VirusApplication
Affected:= 2.16= 4.51= 4.52= 4.61= 4.64= 4.65= 5.0.2= 5.2.1= 5.3.0= 5.5= 5.40= 5.41
F Secure Anti Virus Linux Client SecurityApplication
Affected:<= 5.52
F Secure Anti Virus Linux Server SecurityApplication
Affected:<= 5.52
F Secure Internet SecurityApplication
Affected:= 2005= 2006= 2007
Internet GatekeeperApplication
Affected:<= 6.61= 2.06= 2.14= 2.15.484= 2.16
Solutions Based On F Secure Personal ExpressApplication
Affected:= 6.20

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed F-Secure products
    On Windows, check Add/Remove Programs or the Program Files folder for F-Secure entries. On Linux, run 'rpm -qa | grep -i fsecure' or 'dpkg -l | grep -i fsecure' to list installed F-Secure packages.
    Affected if Any F-Secure product from the affected product list is installed
  2. Check F-Secure Anti-Virus Windows version
    Open the F-Secure Anti-Virus GUI and navigate to About or Settings > Support to view the version number. Alternatively, check the Windows registry key HKLM\SOFTWARE\Data Fellows\F-Secure\Antivirus or look at the executable version properties of the avp.exe or f-secure.exe process.
    Affected if The version equals 2.16, 4.51, 4.52, 4.61, 4.64, 4.65, 5.0.2, 5.2.1, 5.3.0, 5.5, 5.40, or 5.41
  3. Check F-Secure Anti-Virus Linux version
    Run 'f-secure --version' or check the RPM/DEB package version using 'rpm -q f-secure-anti-virus' or 'dpkg -l f-secure-anti-virus'. Look in /opt/f-secure for installation directories.
    Affected if The version is 5.52 or lower (any version up to and including 5.52)
  4. Check F-Secure Internet Security version
    Open the F-Secure Internet Security GUI and check About or Support information. On Windows, also check Add/Remove Programs for the installed version.
    Affected if The version equals 2005, 2006, or 2007
  5. Check F-Secure Internet Gatekeeper version
    Check the installed version through the product interface, or run 'fsgate --version' if available. On Linux, check the RPM/DEB package.
    Affected if The version is 6.61 or lower, or equals 2.06, 2.14, 2.15.484, or 2.16

A user is affected if any F-Secure product from the list is installed and its version matches one of the vulnerable versions specified.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 6.61
Interim mitigation

Update F-Secure anti-virus products to versions released after June 19, 2007 to patch the scanning bypass vulnerability.

Recommended fix Moderate confidence

Any version released after 20070619 (the specific fixed release version should be obtained from F-Secure's official download page)

  1. 1. Identify the currently installed F-Secure product and exact version from the affected list
  2. 2. Visit the official F-Secure support portal at www.f-secure.com to obtain the latest version released after June 2007
  3. 3. Download the appropriate update for your specific F-Secure product (Anti Virus, Internet Security, or Internet Gatekeeper)
  4. 4. Apply the update following F-Secure's standard update procedure
  5. 5. Verify the scanning engine date is post-June 2007 to confirm the vulnerability is addressed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in F Secure Anti Virus Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-3300 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-3300 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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