# CVE-2014-2390: Cross-site request forgery in n/a

> Remote attackers can hijack user sessions to modify accounts in McAfee Network Security Manager via CSRF, requiring user interaction.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-grh6-4r7m-jg4c

## What is CVE-2014-2390?

CVE-2014-2390 is a medium-severity vulnerability in n/a, published on 29 Aug 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in the User Management module in McAfee Network Security Manager (NSM) before 6.1.15.39 7.1.5.x before 7.1.5.15, 7.1.15.x before 7.1.15.7, 7.5.x before 7.5.5.9, and 8.x before 8.1.7.3 allows remote attackers to hijack the authentication of users for requests that modify user accounts via unspecified vectors.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2014-2390?

It affects 1 product.


Products: Mcafee Network Security Manager.

## How do I fix CVE-2014-2390?

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

## Is CVE-2014-2390 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-3965](https://insights.sbomify.com/CVE-2017-3965/): SB10192 - Network Security Management (NSM) - Cross-Site Request Forgery (CSRF) (aka Session Riding) vulnerability (high 8.8)
- [CVE-2017-3972](https://insights.sbomify.com/CVE-2017-3972/): SB10192 - Network Security Management (NSM) - Infrastructure-based foot printing vulnerability (high 8.3)
- [CVE-2017-3969](https://insights.sbomify.com/CVE-2017-3969/): SB10192 - Network Security Management (NSM) - Abuse of communication channels vulnerability (high 8.2)
- [CVE-2017-3971](https://insights.sbomify.com/CVE-2017-3971/): SB10192 - Network Security Management (NSM) - Cryptanalysis vulnerability (high 8.2)
- [CVE-2019-3606](https://insights.sbomify.com/CVE-2019-3606/): Data leakage when in an MDR pair by McAfee Network Security Manager 9.x (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2390 and fix it if it is affected.

What it is: CVE-2014-2390 is a medium-severity vulnerability in n/a, published on 29 Aug 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-2390 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-2014-2390/ (Markdown: https://insights.sbomify.com/CVE-2014-2390/index.md)
```

## Sources

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

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