Comparison Overview
Electrical Engineering Department, Sharif University of Technology
Electrical Engineering Department, Sharif University of Technology
Azadi Ave., Tehran, undefined, undefined, IR
Last Update: 18/12/2025
The Electrical Engineering Department of Sharif University of Technology (SUT) was founded in 1967, one year after the establishment of Sharif University of Technology, in order to address the technical needs of the Iranian industry. While initially offering an undergra...
University of Utah
201 Presidents Circle, ROOM 203, Address 2, Salt Lake City, ut, US, 84112-9008
Last Update: 02/04/2026
The University of Utah, located in Salt Lake City in the foothills of the Wasatch Mountains, is the flagship institution of higher learning in Utah. Founded in 1850, it serves over 31,000 students from across the U.S. and the world. With over 72 major subjects at the un...
Compliance Ranges Comparison
Electrical Engineering Department, Sharif University of Technology
University of Utah
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Electrical Engineering Department, Sharif University of Technology in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for University of Utah in 2026.
Incident History - Electrical Engineering Department, Sharif University of Technology (X = Date, Y = Severity)
Electrical Engineering Department, Sharif University of Technology cyber incidents detection timeline including parent company and subsidiaries.
Incident History - University of Utah (X = Date, Y = Severity)
University of Utah cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Electrical Engineering Department, Sharif University of Technology
University of Utah
FAQ
Latest Global CVEs
PraisonAI before 1.5.115 contains a path traversal vulnerability in MultiAgentMonitor that fails to sanitize agent IDs when building file paths. Attackers can include traversal sequences like ../ in agent IDs to read, write, or overwrite arbitrary files, enabling sensitive disclosure, denial of service, or code execution.
PraisonAI before 1.5.115 contains an information disclosure vulnerability in the MultiAgentLedger component that allows attackers to access sensitive data by registering agents with duplicate IDs. Attackers can exploit the lack of agent ID uniqueness enforcement to share ledger instances and expose system prompts and conversation history between agents.
PraisonAI before 1.5.128 contains a cross-origin agent execution vulnerability in the AGUI endpoint that allows remote attackers to trigger arbitrary agent execution. The POST /agui endpoint lacks authentication and hardcodes Access-Control-Allow-Origin: * headers, combined with Starlette's Content-Type-agnostic JSON parsing, enabling attackers to bypass CORS preflight checks via simple requests and exfiltrate sensitive agent responses including tool execution results and environment data.
PraisonAI before 4.5.128 contains an arbitrary shell command execution vulnerability where the UI modules hardcode approval_mode to auto, overriding administrator configuration from PRAISON_APPROVAL_MODE environment variable. Authenticated attackers can instruct the LLM agent to execute arbitrary shell commands via subprocess.run with shell=True, bypassing the manual approval gate and insufficient command sanitization blocklists.
PraisonAI before 1.5.128 caches tool approval decisions by tool name only, not by invocation arguments, allowing subsequent execute_command calls to bypass approval prompts. Attackers can exploit this by obtaining initial approval for a benign command, then silently exfiltrate API keys and credentials via subsequent shell commands without user consent.