# CVE-2019-3479: Code injection in ArcSight Logger

> Attackers can achieve remote code execution in ArcSight Logger, requiring an upgrade to mitigate the vulnerability.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9cmf-ch3x-4cjx

## What is CVE-2019-3479?

CVE-2019-3479 is a critical code injection vulnerability in ArcSight Logger, published on 25 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mitigates a potential remote code execution issue in ArcSight Logger versions prior to 6.7.

## Which versions are affected by CVE-2019-3479?

It affects 1 product.


Products: Hp Arcsight Logger.

## How do I fix CVE-2019-3479?

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

## Is CVE-2019-3479 being exploited?

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

## Other vulnerabilities in ArcSight Logger

- [CVE-2014-7884](https://insights.sbomify.com/CVE-2014-7884/): Other in n/a (critical 9.0)
- [CVE-2019-11655](https://insights.sbomify.com/CVE-2019-11655/): File upload in ArcSight Logger. (high 8.8)
- [CVE-2019-3484](https://insights.sbomify.com/CVE-2019-3484/): Code injection in ArcSight Logger (high 7.8)
- [CVE-2015-6863](https://insights.sbomify.com/CVE-2015-6863/): Code injection in n/a (high 7.3)
- [CVE-2019-3481](https://insights.sbomify.com/CVE-2019-3481/): XML external entity in ArcSight Logger (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-3479 and fix it if it is affected.

What it is: CVE-2019-3479 is a critical code injection vulnerability in ArcSight Logger, published on 25 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-3479 in the wild and no public exploit code.

Affected product: ArcSight Logger. 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-2019-3479/ (Markdown: https://insights.sbomify.com/CVE-2019-3479/index.md)
```

## Sources

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

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