Comparison Overview
Boston University Federal Relations

Boston University Federal Relations
701 8th Street, NW, Washington, 20001, US
Last Update: 01/12/2025
BU Federal Relations advocates for Boston University priorities, such as student aid, research, and the humanities, with federal policymakers.

Arizona State University
1151 S Forest Ave, Tempe, AZ, US, 85281
Last Update: 18/08/2026
ASU has developed a new model for the American research university, creating an institution committed to excellence, access and impact — the New American University. Nationally and internationally acclaimed, ASU ranks among the very best in nearly every critical measu...
Compliance Ranges Comparison

Boston University Federal Relations







Arizona State University






Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Boston University Federal Relations in 2026.
Incidents vs Higher Education Industry Avg (This Year)
Arizona State University has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Boston University Federal Relations (X = Date, Y = Severity)
Boston University Federal Relations cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Arizona State University (X = Date, Y = Severity)
Arizona State University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Boston University Federal Relations

Arizona State 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.