# CVE-2014-4823: Command injection in n/a

> Remote attackers with administrative access can inject system commands into the IBM Security Access Manager administration console, leading to code execution.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hp3h-5542-vq2g

## What is CVE-2014-4823?

CVE-2014-4823 is a critical command injection vulnerability in n/a, published on 3 Oct 2014. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The administration console in IBM Security Access Manager for Web 7.x before 7.0.0-ISS-WGA-IF0009 and 8.x before 8.0.0-ISS-WGA-FP0005, and Security Access Manager for Mobile 8.x before 8.0.0-ISS-ISAM-FP0005, allows remote attackers to inject system commands via unspecified vectors.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 5 products.


Products: Ibm Security Access Manager for Mobile 8.0 Firmware, Ibm Security Access Manager for Mobile Appliance, Ibm Security Access Manager for Web 7.0 Firmware, Ibm Security Access Manager for Web 8.0 Firmware, Ibm Security Access Manager for Web Appliance.

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

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

## Is CVE-2014-4823 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-4823 is a critical command injection vulnerability in n/a, published on 3 Oct 2014. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-4823 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-4823/ (Markdown: https://insights.sbomify.com/CVE-2014-4823/index.md)
```

## Sources

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

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