Comparison Overview
Oxford University Clinical Research Unit

Oxford University Clinical Research Unit
Oxford Univeristy Clinical Research Unit,, Ho Chi Minh City, 70000, VN
Last Update: 31/03/2026
The Oxford University Clinical Research Unit (OUCRU) is a large-scale clinical and public health research unit with site offices in Viet Nam, Indonesia, and Nepal. Part of the Centre for Tropical Medicine and Global Health at the University of Oxford (UK), OUCRU was fi...

CNRS
3 rue Michel-Ange, Paris, 75016, FR
Last Update: 01/04/2026
The French National Centre for Scientific Research is among the world's leading research institutions. Its scientists explore the living world, matter, the Universe, and the functioning of human societies in order to meet the major challenges of today and tomorrow. Inte...
Compliance Ranges Comparison

Oxford University Clinical Research Unit







CNRS






Benchmark & Cyber Underwriting Signals
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for Oxford University Clinical Research Unit in 2026.
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for CNRS in 2026.
Incident History - Oxford University Clinical Research Unit (X = Date, Y = Severity)
Oxford University Clinical Research Unit cyber incidents detection timeline including parent company and subsidiaries.
Incident History - CNRS (X = Date, Y = Severity)
CNRS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Oxford University Clinical Research Unit

CNRS
FAQ
Latest Global CVEs
A vulnerability has been found in SourceCodester Simple Online Food Ordering System 1.0. This affects an unknown function of the file /admin/ajax.php?action=login2. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
A flaw was found in the ipa_getkeytab module of the community.general Ansible collection. The module's bind_pw parameter, used to supply the LDAP simple-bind password when retrieving a Kerberos keytab, is not declared with no_log, unlike the sibling password parameter in the same module. As a consequence, the supplied IPA/LDAP bind password is recorded in cleartext in the managed host's system journal/syslog (the module's "Invoked with" record), is included in the module's return values and verbose (-v) output, and is displayed in Automation Controller / AWX job output. The password is additionally passed on the command line to the ipa-getkeytab helper (as --bindpw <value>), exposing it in the process list to local users while the command runs. An attacker able to read these logs, job output, or the process table can obtain the directory bind credential, potentially compromising the accounts and objects that credential can access.
The device metadata import interface /device/instance/{productId}/property-metadata/import of jetlinks community 2.11 is vulnerable to Server-side request forgery (SSRF).
disconf (Distributed Configuration Management Platform) 2.6.36 is vulnerable to Incorrect Access Control. The config-fetching APIs /api/config/item, /api/config/file, /api/config/list and /api/config/simple/list are exposed without authentication. The LoginInterceptor explicitly whitelists these four paths, so any anonymous attacker can read every configuration item and configuration file managed by the config center.
Funiture 1.0.0 is vulnerable to SQL Injection in the backend tool interfaces /sys/tool/select.json and /sys/tool/update.json.