Comparison Overview
OYO LIFE India

OYO LIFE India
Sector 69, Gurugram, Haryana, 122001, IN
Last Update: 04/12/2025
𝗡𝗼𝘄 𝗰𝗵𝗼𝗼𝘀𝗲 𝗢𝗬𝗢 𝗟𝗶𝗳𝗲 𝗳𝗼𝗿 𝘆𝗼𝘂𝗿 𝗹𝗼𝗻𝗴 𝘁𝗲𝗿𝗺 𝗿𝗲𝗻𝘁𝗮𝗹 𝗻𝗲𝗲𝗱𝘀 𝗢𝗬𝗢𝗟𝗶𝗳𝗲.𝗶𝗻 | +𝟵𝟭-𝟵𝟬𝟲𝟵𝟬𝟬𝟬𝟮𝟯𝟰 F𝘂𝗿𝗻𝗶𝘀𝗵𝗲𝗱 and sanitised spaces 𝗮𝘁 𝗶𝗱𝗲𝗮𝗹 𝗹𝗼𝗰𝗮𝘁𝗶𝗼𝗻𝘀 𝗮𝗰𝗿𝗼𝘀𝘀 𝗕𝗮𝗻𝗴𝗮𝗹𝗼𝗿𝗲, 𝗣𝘂𝗻𝗲, 𝗡𝗼𝗶...

DoubleTree by Hilton
7930 Jones Branch Drive, McLean, US
Last Update: 03/04/2026
DoubleTree by Hilton hotels are distinctively designed properties that provide true comfort to today’s business and leisure travelers. From the millions of delighted hotel guests who are welcomed with the brand’s legendary, warm chocolate chip cookies at check-in to the...
Compliance Ranges Comparison

OYO LIFE India







DoubleTree by Hilton






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for OYO LIFE India in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for DoubleTree by Hilton in 2026.
Incident History - OYO LIFE India (X = Date, Y = Severity)
OYO LIFE India cyber incidents detection timeline including parent company and subsidiaries.
Incident History - DoubleTree by Hilton (X = Date, Y = Severity)
DoubleTree by Hilton cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

OYO LIFE India

DoubleTree by Hilton
FAQ
Latest Global CVEs
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in David Lingren Media LIbrary Assistant allows Stored XSS. This issue affects Media LIbrary Assistant: from n/a through 3.39.
Missing Authorization vulnerability in Kings Plugins B2BKing allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects B2BKing: from n/a through 5.2.30.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in PublishPress PublishPress Series allows Stored XSS. This issue affects PublishPress Series: from n/a through 2.17.0.
linuxfabrik-lib provides Python modules for database access, caching, shell execution, and API integrations, and Linuxfabrik Monitoring Plugins uses its shared testing helper across check plugins. Prior to linuxfabrik-lib 6.1.0 and Linuxfabrik Monitoring Plugins 7.0.0, lib.lftest.test() treated the first or second element of a --test CSV argument as a filesystem path and returned the file contents as simulated standard output or standard error without path confinement. The hidden but production-accessible --test argument was accepted by sudo-authorized plugins, so an attacker controlling the nagios or icinga account could use check-plugins/deb-updates/deb-updates with its default QUERY=1 to disclose every line of a root-readable file. Approximately 22 other plugins exposed filtered content or a root file existence and readability oracle through the same helper, while check-plugins/network-bonding/network-bonding and check-plugins/openstack-swift-stat/openstack-swift-stat had direct read paths that bypassed the helper. The library fix confines fixture reads to the invoking plugin's unit-test directory and refuses unsafe anchors, and the plugin fix routes the two bypasses through that helper. These issues are fixed in linuxfabrik-lib 6.1.0 and Linuxfabrik Monitoring Plugins 7.0.0.
- https://github.com/Linuxfabrik/lib/commit/d665042c55fae83a295ebc0023e8b77f6c473a28
- https://github.com/Linuxfabrik/lib/releases/tag/v6.1.0
- https://github.com/Linuxfabrik/monitoring-plugins/commit/f6680a9e4b39569f318feefdb2f51e5d18c7dad5
- https://github.com/Linuxfabrik/monitoring-plugins/releases/tag/v7.0.0
- https://github.com/Linuxfabrik/monitoring-plugins/security/advisories/GHSA-rh9c-rqvg-f7pr
Linuxfabrik Monitoring Plugins provides monitoring plugins for Icinga, Nagios, and related systems. Prior to version 7.0.0, check-plugins/logfile/logfile accepted a free-form --filename path and opened it as root when invoked through the shipped nagios or icinga sudoers allowlist, without confining the resolved path to /var/log. An attacker who controls the monitoring account can select a root-readable file such as /etc/shadow and use --warning-regex . while leaving SUPPRESS_OUTPUT false, causing each nonempty line to be collected in warn_matches and returned through lib.base.oao(). The vulnerable flow passes the expanded scan_path directly to open(), and neither real-path containment nor an allowlist protects the sink. The same fix also confines mysql-logfile and openvpn-client-list paths, allows only documented log roots, and resolves symlinks and parent-directory traversal before checking containment. This issue is fixed in version 7.0.0.
- https://github.com/Linuxfabrik/monitoring-plugins/blob/ae486fc629e1ca9373e1b6dd5e395603ee453bbc/CHANGELOG.md#v700---2026-08-14
- https://github.com/Linuxfabrik/monitoring-plugins/commit/a0ca1268d84e0caf10442b9c7477d699b52d1c92
- https://github.com/Linuxfabrik/monitoring-plugins/releases/tag/v7.0.0
- https://github.com/Linuxfabrik/monitoring-plugins/security/advisories/GHSA-f54c-p5vg-mr5c