# CVE-2011-0548: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via a crafted PRZ file in Symantec mail security products.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Jul 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hrw2-pv4c-v3hp

## What is CVE-2011-0548?

CVE-2011-0548 is a critical memory corruption vulnerability in n/a, published on 18 Jul 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in the Lotus Freelance Graphics PRZ file viewer in Autonomy KeyView, as used in Symantec Mail Security (SMS) 6.x through 8.x, Symantec Brightmail and Messaging Gateway before 9.5.1, and Symantec Data Loss Prevention (DLP) before 10.5.3 and 11.x before 11.1, allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted .prz file.  NOTE: this may overlap CVE-2011-1217.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2011-0548?

It affects 3 products.


Products: Symantec Brightmail and Messaging Gateway, Symantec Data Loss Prevention, Symantec Mail Security.

## How do I fix CVE-2011-0548?

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

## Is CVE-2011-0548 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0548 and fix it if it is affected.

What it is: CVE-2011-0548 is a critical memory corruption vulnerability in n/a, published on 18 Jul 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-0548 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-2011-0548/ (Markdown: https://insights.sbomify.com/CVE-2011-0548/index.md)
```

## Sources

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

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