# CVE-2013-4602: Denial of service in n/a

> An attacker can cause a denial of service via an infinite loop in the PDF Scanner Engine of Avira AntiVir.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4ghf-h9pg-hhpp

## What is CVE-2013-4602?

CVE-2013-4602 is a medium-severity denial of service vulnerability in n/a, published on 12 Feb 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A Denial of Service (infinite loop) vulnerability exists in Avira AntiVir Engine before 8.2.12.58 via an unspecified function in the PDF Scanner Engine.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2013-4602?

It affects 10 products.


Products: Avira Antivir Mailgate, Avira Antivir Mailgate Suite, Avira Antivir Personal, Avira Antivir Sharepoint, Avira Antivir Webgate, Avira Antivir Webgate Suite, Avira Antivirus Server, Avira Exchange Security, Avira Professional Security, Avira Savapi.

## How do I fix CVE-2013-4602?

No fix has been published for CVE-2013-4602 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-4602 being exploited?

There is no known exploitation of CVE-2013-4602 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4602 and fix it if it is affected.

What it is: CVE-2013-4602 is a medium-severity denial of service vulnerability in n/a, published on 12 Feb 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-4602 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-4602/ (Markdown: https://insights.sbomify.com/CVE-2013-4602/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-4602
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-4602
- OSV: https://osv.dev/vulnerability/CVE-2013-4602

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-4602/
Summaries are generated and may contain mistakes; the official description above is the record.