Comparison Overview
Johns Hopkins Biomedical Engineering

Johns Hopkins Biomedical Engineering
undefined, Baltimore, MD, 21218, US
Last Update: 05/12/2025
Established in 1961, the Johns Hopkins Department of Biomedical Engineering (BME) is home to the nation’s first training program in the field. Consistently ranked the #1 BME department in the country, our mission is to advance human health by training biomedical enginee...

Deakin University
221 Burwood Highway, Burwood, victoria, AU, 3125
Last Update: 29/03/2026
Deakin’s unique identity – rooted in balanced excellence in education and research – has been driving lasting change for a better future since 1974. Over our 50+ year history, Deakin has grown to be one of the top universities worldwide with a truly global presence. Our...
Compliance Ranges Comparison

Johns Hopkins Biomedical Engineering







Deakin University






Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Johns Hopkins Biomedical Engineering in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Deakin University in 2026.
Incident History - Johns Hopkins Biomedical Engineering (X = Date, Y = Severity)
Johns Hopkins Biomedical Engineering cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Deakin University (X = Date, Y = Severity)
Deakin University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Johns Hopkins Biomedical Engineering

Deakin University
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.