CVE-2023-27497
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 · uneditedDue to missing authentication and input sanitization of code the EventLogServiceCollector of SAP Diagnostics Agent - version 720, allows an attacker to execute malicious scripts on all connected Diagnostics Agents running on Windows. On successful exploitation, the attacker can completely compromise confidentiality, integrity and availability of the system.
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 · high confidenceThe EventLogServiceCollector in SAP Diagnostics Agent version 720 lacks authentication and input sanitization, allowing unauthenticated attackers to inject and execute malicious scripts on all connected Windows-based Diagnostics Agents. This command injection vulnerability enables full system compromise.
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= 720CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 if SAP Diagnostics Agent is installedCheck for SAP Diagnostics Agent installation by looking for its installation directory (typically under C:\Program Files\SAP\ or C:\SAP\), or check Windows Services for 'SAP Diagnostics Agent' serviceAffected if SAP Diagnostics Agent is present on the system
-
Verify the installed version is 720Check the Diagnostics Agent version - this can typically be found in the agent's about or version information, often accessible via the SAP LM or in the installation directory's version fileAffected if Installed version is exactly 720
-
Identify if EventLogServiceCollector component is runningCheck if the EventLogServiceCollector is active - this may be visible in the Diagnostics Agent's component list, running processes, or exposed ports used by the agent for log collectionAffected if EventLogServiceCollector component is running or exposed
-
Verify if the vulnerability is presentAttempt to access the EventLogServiceCollector endpoint without credentials - if authentication is not enforced and the service accepts unauthenticated requests, the system is vulnerableAffected if EventLogServiceCollector accepts unauthenticated requests without requiring authentication credentials
The system is affected if SAP Diagnostics Agent version 720 is installed AND the EventLogServiceCollector component is running without requiring authentication
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 SAP security patch for CVE-2023-27497 to all affected Diagnostics Agents running version 720. Verify that authentication is now enforced and input validation prevents script injection.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27497 — 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-2023-27497 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