CVE-2018-2460 json
SAP Business One Android application, version 1.2, does not verify the certificate properly for HTTPS connection.
published 8y ago modified 4mo ago also EUVD-2018-14315
- cvss
- 5.9
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
SAP Business One Android application, version 1.2, does not verify the certificate properly for HTTPS connection. This allows attacker to do MITM attack.
Is CVE-2018-2460 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.77% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.9 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Affected products
- SAP SAP Business One Android application
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
wiki.scn.sap.com
/wiki/pages/viewpage.action?pageId=499356993
vendor-advisory
-
launchpad.support.sap.com
/#/notes/2682503
permissions-required, vendor-advisory
-
securityfocus.com
/bid/105309
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-2460
- NVD CVE-2018-2460
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.