CVE-2019-0379
First published: Tue Oct 08 2019(Updated: )
SAP Process Integration, business-to-business add-on, versions 1.0, 2.0, does not perform authentication check properly when the default security provider is changed to BouncyCastle (BC), leading to Missing Authentication Check
Credit: cna@sap.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| SAP NetWeaver Process Integration | =1.0 | |
| SAP NetWeaver Process Integration | =2.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-0379?
CVE-2019-0379 is rated as high severity due to the potential for unauthorized access caused by a missing authentication check.
How do I fix CVE-2019-0379?
To fix CVE-2019-0379, ensure that the default security provider remains unchanged from BouncyCastle and implement proper authentication checks.
What versions of SAP Process Integration are affected by CVE-2019-0379?
CVE-2019-0379 affects SAP Process Integration versions 1.0 and 2.0.
What could an attacker do if they exploit CVE-2019-0379?
An attacker exploiting CVE-2019-0379 could gain unauthorized access to sensitive business data.
Is there a workaround for CVE-2019-0379 until a patch is applied?
Disabling or reverting to the default security provider can serve as a temporary workaround for CVE-2019-0379.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/weakness
- agent/severity
- agent/last-modified-date
- agent/first-publish-date
- agent/description
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/sap
- canonical/sap netweaver process integration
- version/sap netweaver process integration/1.0
- version/sap netweaver process integration/2.0