Hospitality Res 3700 vulnerabilitiesRanked by how likely they are to be used.
Hospitality Res 3700 is made by Oracle. We track 5 published vulnerabilities listed under that exact name, across 3 versions. None of them is on the list of flaws known to be exploited today. Oracle lists newer releases under their own names, such as Hospitality Res 3700 Firmware, so check those pages too.
We keep watching the known-exploited list.
Is Hospitality Res 3700 listed under other names? Yes.
Oracle also lists Hospitality Res 3700 under more specific names, such as Hospitality Res 3700 Firmware. 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 Hospitality Res 3700 vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Hospitality Res 3700's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Hospitality Res 3700 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.
- 14%CVE-2019-3025Critical
Vulnerability in the Oracle Hospitality RES 3700 component of Oracle Food and Beverage Applications.
- 7.1%CVE-2018-20843High
In libexpat in Expat before 2.2.7, XML input including XML names that contain a large number of colons could make the XML parser consume a high amount of RAM and CPU resources while processing (enough to be usable...
- 1.7%CVE-2020-14783Medium
Vulnerability in the Oracle Hospitality RES 3700 product of Oracle Food and Beverage Applications (component: CAL).
- 0.5%CVE-2017-10225High
Vulnerability in the Oracle Hospitality RES 3700 component of Oracle Hospitality Applications (subcomponent: OPS Operations).
- 0.4%CVE-2017-10221Medium
Vulnerability in the Oracle Hospitality RES 3700 component of Oracle Hospitality Applications (subcomponent: OPS Operations).
Running Hospitality Res 3700? 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
Vulnerability in the Oracle Hospitality RES 3700 component of Oracle Food and Beverage Applications. The supported version that is affected is 5.7. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Hospitality RES 3700. While the vulnerability is in Oracle Hospitality RES 3700, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Oracle Hospitality RES 3700. CVSS 3.0 Base Score 9.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H).
- Matched to
- Hospitality Res 3700 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 Hospitality Res 3700, across 3 versions.
None of Hospitality Res 3700's vulnerabilities is on the list of flaws known to be exploited today.
Oracle also lists Hospitality Res 3700 under more specific names, such as Hospitality Res 3700 Firmware. 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 Hospitality Res 3700. 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.