Comparison Overview
Boston University Sustainability

Boston University Sustainability
Boston, US
Last Update: 24/12/2025
We support the transformation of Boston University’s planning, operations, and culture toward a sustainable and equitable future. We are guided by the University’s mission, Strategic Plan, and Climate Action Plan.

Virginia Commonwealth University
910 W Franklin St, Richmond, va, US, 23284-2512
Last Update: 02/04/2026
We’re Virginia Commonwealth University — the university FOR Virginia. You will see an incredible mix of attitudes, styles and stories. Inclusion is our heartbeat and it drives us to tackle difficult challenges others can’t or won’t. We do things differently here, be...
Compliance Ranges Comparison

Boston University Sustainability







Virginia Commonwealth University






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

Boston University Sustainability

Virginia Commonwealth University
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.