# CVE-2016-3647: Server-side request forgery in n/a

> Authenticated attackers can exploit SSRF in Symantec Endpoint Protection Manager to access internal network resources.

- **Severity:** High 7.7 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g6gm-vj99-4x7p

## What is CVE-2016-3647?

CVE-2016-3647 is a high-severity server-side request forgery vulnerability in n/a, published on 30 Jun 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Symantec Endpoint Protection Manager (SEPM) 12.1 before RU6 MP5 allows remote authenticated users to conduct server-side request forgery (SSRF) attacks, and trigger network traffic to arbitrary intranet hosts, via a crafted request.

## Which versions are affected by CVE-2016-3647?

It affects 1 product.


Products: Symantec Endpoint Protection Manager.

## How do I fix CVE-2016-3647?

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

## Is CVE-2016-3647 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-3648](https://insights.sbomify.com/CVE-2016-3648/): Security feature bypass in n/a (high 8.8)
- [CVE-2016-3650](https://insights.sbomify.com/CVE-2016-3650/): Information disclosure in n/a (high 8.8)
- [CVE-2015-8153](https://insights.sbomify.com/CVE-2015-8153/): SQL injection in n/a (high 8.8)
- [CVE-2015-8154](https://insights.sbomify.com/CVE-2015-8154/): Privilege escalation in n/a (high 8.8)
- [CVE-2015-6555](https://insights.sbomify.com/CVE-2015-6555/): Code injection in n/a (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-3647 and fix it if it is affected.

What it is: CVE-2016-3647 is a high-severity server-side request forgery vulnerability in n/a, published on 30 Jun 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-3647 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-2016-3647/ (Markdown: https://insights.sbomify.com/CVE-2016-3647/index.md)
```

## Sources

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

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