CVE-2014-2748
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Security Audit Log facility in SAP Enhancement Package 6 for SAP ERP 6.0 contains a vulnerability that allows remote attackers to modify or delete arbitrary log classes via unspecified vectors. This compromises the integrity of security audit logs, potentially allowing attackers to conceal their activities by altering or removing forensic evidence.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify SAP ERP version and Enhancement Package levelExecute transaction SA01 or use SAP system info (SM51) to determine if the system is running SAP ERP 6.0 with Enhancement Package 6 (EHP6). Verify the exact SP stack version via system report.Affected if The system is running SAP ERP 6.0 with Enhancement Package 6 (EHP6) at any SP level.
-
Confirm Security Audit Log is configuredAccess transaction SM19 to view the Security Audit Log configuration status. Check whether audit logging is active and which log classes are currently defined.Affected if Security Audit Log is enabled and log classes are defined in the system.
-
Verify access controls on SM19 and SM20Use transaction SU53 immediately after attempting to access SM19 (Security Audit Log configuration) and SM20 (Security Audit Log analysis) to check user authorization. Review SAP role assignments for users with access to these transactions.Affected if Users beyond authorized security administrators have access to SM19 or SM20 transactions.
-
Inspect recent Security Audit Log configuration changesReview logs in transaction SM20 or external SIEM systems for any modifications to log classes (creation, deletion, or modification of audit classes) that were not performed by known security administrators.Affected if Unauthorized or unexpected modifications to audit log classes are present in recent logs.
You are affected if your system runs SAP ERP 6.0 with Enhancement Package 6 and the Security Audit Log is active, regardless of whether you observe exploitation, because the vulnerability allows arbitrary modification of log classes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the relevant SAP security patch for CVE-2014-2744/CVE-2014-2748 when available. In the interim, monitor and restrict access to the Security Audit Log configuration transactions (such as SM19 and SM20) and implement additional logging of audit log configuration changes through external SIEM solutions.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2748 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-2748 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data