CVE-2007-1671
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 · uneditedavpack32.dll before 7.3.0.6 in Avira AntiVir allows remote attackers to cause a denial of service (infinite loop) via a ZOO archive with a direntry structure that points to a previous file.
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 avpack32.dll library in Avira AntiVir versions before 7.3.0.6 contains a denial-of-service vulnerability when parsing ZOO archive files. A malformed ZOO archive containing a direntry structure that points to a previous file causes an infinite loop in the parsing routine, consuming CPU resources and rendering the antivirus product unresponsive.
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.5CVSS 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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Verify Avira AntiVir is installedCheck for Avira AntiVir installation directory (typically C:\Program Files\Avira\AntiVir Desktop\ or similar) and locate the version information in the product's about or update sectionAffected if Avira AntiVir Personal version 7.3.0.5 or earlier is installed
-
Check avpack32.dll versionLocate avpack32.dll in the AntiVir installation directory, right-click and view Properties > Details to see file version, or run: dir C:\Program Files\Avira\AntiVir Desktop\avpack32.dllAffected if avpack32.dll version is earlier than the version bundled with 7.3.0.6 (file version below 7.3.0.6)
-
Confirm ZOO archive scanning is enabledOpen AntiVir configuration, look under 'Archive scanning' or 'Scanner' settings to verify if scanning of archive files including ZOO archives is enabledAffected if ZOO archive scanning is enabled (default behavior scans archives)
-
Check installed version against affected rangeCompare your specific AntiVir Personal version number to the affected range: any version <= 7.3.0.5 is vulnerable; version 7.3.0.6 and later are fixedAffected if Installed version is 7.3.0.5 or earlier
If Avira AntiVir Personal version 7.3.0.5 or earlier is installed with avpack32.dll prior to the 7.3.0.6 update, and ZOO archive scanning is enabled, the environment is affected by this CVE.
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 Avira AntiVir to version 7.3.0.6 or later which includes the patched avpack32.dll library that properly validates direntry structures in ZOO archives to prevent infinite loop conditions.
- 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-2007-1671 — 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-2007-1671 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