Sap R 3 vulnerabilitiesRanked by how likely they are to be used.
Sap R 3 is made by SAP. We track 5 published vulnerabilities listed under that exact name, across 7 versions. None of them is on the list of flaws known to be exploited today. SAP lists newer releases under their own names, such as Sap R 3 Web Application Server Demo, so check those pages too.
We keep watching the known-exploited list.
Is Sap R 3 listed under other names? Yes.
SAP also lists Sap R 3 under more specific names, such as Sap R 3 Web Application Server Demo. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Sap R 3 vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Sap R 3's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Sap R 3 flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.7%CVE-2002-1578High
The default installation of SAP R/3, when using Oracle and SQL*net V2 3.x, 4.x, and 6.10, allows remote attackers to obtain arbitrary, sensitive SAP data by directly connecting to the Oracle database and executing...
- 2.6%CVE-2005-4815High
SAP 6.4 before 6.40 patch 4, 6.2 before 6.20 patch 1364, 4.6 before 4.6D patch 1767, 45 before 45B patch 913, 40 before 40B patch 1008, and 31 before 31I patch 735 do not properly restrict process execution by...
- 1.5%CVE-2003-1035High
The default installation of SAP R/3 46C/D allows remote attackers to bypass account locking by using the RFC API instead of the SAPGUI to conduct a brute force password guessing attack, which does not lock out the...
- 1.5%CVE-2005-1691Medium
Directory traversal vulnerability in Internet Graphics Server in SAP before 6.40 Patch 11 allows remote attackers to read arbitrary files via ".." sequences in an HTTP GET request.
- 1.3%CVE-2002-1577High
SAP R/3 2.0B to 4.6D installs several clients with default users and passwords, which allows remote attackers to gain privileges via the (1) SAP*, (2) SAPCPIC, (3) DDIC, (4) EARLYWATCH, or (5) TMSADM accounts.
Running Sap R 3? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
The default installation of SAP R/3, when using Oracle and SQL*net V2 3.x, 4.x, and 6.10, allows remote attackers to obtain arbitrary, sensitive SAP data by directly connecting to the Oracle database and executing queries against the database, which is not password-protected.
- Matched to
- Sap R 3 on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 5 published vulnerabilities listed under the name Sap R 3, across 7 versions.
None of Sap R 3's vulnerabilities is on the list of flaws known to be exploited today.
SAP also lists Sap R 3 under more specific names, such as Sap R 3 Web Application Server Demo. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Sap R 3. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.