# CVE-2011-2779: Missing authorization in n/a

> Local attackers can modify or delete log data due to world-writable permissions on exported report files in HP ArcSight Connector Appliance.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p5qq-87j3-wxwp

## What is CVE-2011-2779?

CVE-2011-2779 is a low-severity missing authorization vulnerability in n/a, published on 19 Jul 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Windows Event Log SmartConnector in HP ArcSight Connector Appliance before 6.1 uses world-writable permissions for exported report files, which allows local users to change or delete log data by modifying a file, a different vulnerability than CVE-2011-0770.

Weakness: CWE-264

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

It affects 7 products.


Products: Hp Arcsight C1000 Appliance, Hp Arcsight C1300 Appliance, Hp Arcsight C3200 Appliance, Hp Arcsight C3400 Appliance, Hp Arcsight C5200 Appliance, Hp Arcsight C5400 Appliance, Hp Windows Event Log Smartconnector.

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

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

## Is CVE-2011-2779 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-0770](https://insights.sbomify.com/CVE-2011-0770/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2779 is a low-severity missing authorization vulnerability in n/a, published on 19 Jul 2011. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-2779 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-2779/ (Markdown: https://insights.sbomify.com/CVE-2011-2779/index.md)
```

## Sources

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

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