|
|
|
Vulnerability Report: SAP R/3
|
This vulnerability report for SAP R/3 contains a complete overview of all Secunia advisories affecting it. You can use this vulnerability report to ensure that you are aware of all vulnerabilities, both patched and unpatched, affecting this product allowing you to take the necessary precautions.
If you have information about a new or an existing vulnerability in SAP R/3 then you are more than welcome to contact us.
|
|
|
|
|
Vendor, Links, and Unpatched Vulnerabilities
| Vendor |
SAP
|
|
|
Product Link
|
View Here (Link to external site)
|
|
|
Affected By
|
6 Secunia advisories
7 Vulnerabilities
|
|
|
Monitor Product
|
Receive alerts for this product
|
|
|
Unpatched
|
17% (1 of 6 Secunia advisories)
|
|
Most Critical Unpatched
The most severe unpatched Secunia advisory affecting SAP R/3, with all vendor patches applied, is rated Not critical  .
|
|
|
|
|
|
1 Secunia Advisories in 2003
|
Secunia has issued a total of 1 Secunia advisories in 2003 for SAP R/3. Currently, 100% (1 out of 1) are marked as unpatched with the most severe being rated Not critical
More information about the specific Secunia advisories affecting SAP R/3 can be found below. Each Secunia advisory is enclosed by a box highlighted with a color representing its current patch status. You can read the complete Secunia advisories for thorough descriptions of the issues covered and for solution suggestions by clicking either the Secunia advisory title or the "Read More" links available for each Secunia advisory.
|
|
|
|
|
|
Release Date:
2003-03-05 |
Secunia Advisory ID:
SA8216 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
Brute force
|
Where:
From local network |
|
Short Description:
SAP R/3 locks out accounts if there is 12 failed login attempts. However applications that use the RFC API are not limited by this, thus applications which use the RFC API could allow users to brute force accounts. [Read More]
|
|
|
|
