# CVE-2014-2748: Missing authorization in n/a

> Remote attackers with high privileges can modify or delete arbitrary security audit log classes in SAP ERP.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fcgf-3g9q-p3r9

## What is CVE-2014-2748?

CVE-2014-2748 is a high-severity missing authorization vulnerability in n/a, published on 10 Apr 2014. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Security Audit Log facility in SAP Enhancement Package (EHP) 6 for SAP ERP 6.0 allows remote attackers to modify or delete arbitrary log classes via unspecified vectors.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-264

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

It affects 1 product.


Products: Sap Enhancement Package.

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

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

## Is CVE-2014-2748 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2748 is a high-severity missing authorization vulnerability in n/a, published on 10 Apr 2014. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-2748 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-2748/ (Markdown: https://insights.sbomify.com/CVE-2014-2748/index.md)
```

## Sources

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

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