CVE-2018-2425
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 · uneditedUnder certain conditions, SAP Business One, 9.2, 9.3, for SAP HANA backup service allows an attacker to access information which would otherwise be restricted.
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 confidenceInformation disclosure vulnerability in SAP Business One's HANA backup service (versions 9.2, 9.3) where, under certain conditions, an attacker can bypass access restrictions and view sensitive data that should be protected.
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= 9.2= 9.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm SAP Business One versionQuery the SAP Business One version from the system: use the Version Info function in SAP Business One (Help > Version Info) or query via SQL: SELECT * FROM SBO_Common..OADM. Check if the version is 9.2 or 9.3.Affected if Installed version is exactly 9.2 or 9.3
-
Verify HANA database is in useConfirm the underlying database is SAP HANA. In SAP Business One, go to Database Upgrade/Replication settings, or check via SQL: SELECT * FROM SBO_Common..OADM WHERE DbType = 'hana' or verify HANA connection parameters in the license manager.Affected if The system uses SAP HANA as its database platform
-
Confirm HANA backup service is configuredCheck if HANA backup functionality is enabled. In SAP Business One, navigate to Administration > System Initialization > Backup/Restore, or check HANA Studio for backup configuration. Look for active backup schedules or backup files present on the system.Affected if HANA backup service is enabled and configured on the system
-
Inspect backup service access controlsReview user authorizations for backup operations in SAP Business One: go to Administration > System Initialization > Authorizations > Authorization Management. Verify if unauthenticated or low-privilege users can access backup data or backup file locations.Affected if Backup service access restrictions are weak, misconfigured, or can be bypassed by low-privilege users
A system is affected if it runs SAP Business One version 9.2 or 9.3 with an underlying SAP HANA database where the backup service is enabled and access controls can be bypassed to view sensitive backup data.
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-2018-2425; review and restrict network access to the SAP HANA backup service; verify proper authentication and authorization controls are enforced for backup operations.
- Consultation3.0 h
- Implementation5.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-2425 — 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-2018-2425 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