Comparison Overview
PT Jasa Marga (Persero) Tbk

PT Jasa Marga (Persero) Tbk
Plaza Tol Taman Mini Indonesia Indah, East Jakarta, 13550, ID
Last Update: 03/04/2026
To support the economic growth, on March 1, 1978, the Government issued Regulation number 4 year 1978 on the establishment of PT Jasa Marga (persero) Tbk. Indonesia to provide a reliable road network in the country. Jasa Marga's 1978-constructed Jakarta-Bogor-Ciawi To...

UPS
55 Glenlake Parkway, NE, Atlanta, 30328, US
Last Update: 07/10/2026
Operating in more than 200 countries and territories, we’re committed to moving our world forward by delivering what matters. Beginning as a small messenger service, UPS was started by two enterprising teenagers and a $100 loan. Now, we’re almost 500,000 UPSers strong, ...
Compliance Ranges Comparison

PT Jasa Marga (Persero) Tbk







UPS






Benchmark & Cyber Underwriting Signals
Incidents vs Truck Transportation Industry Avg (This Year)
No incidents recorded for PT Jasa Marga (Persero) Tbk in 2026.
Incidents vs Truck Transportation Industry Avg (This Year)
UPS has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - PT Jasa Marga (Persero) Tbk (X = Date, Y = Severity)
PT Jasa Marga (Persero) Tbk cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UPS (X = Date, Y = Severity)
UPS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

PT Jasa Marga (Persero) Tbk

UPS
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.