Comparison Overview
PetroChina International Iraq FZE Iraq Branch

PetroChina International Iraq FZE Iraq Branch
PetroChina Halfaya Base Camp, Kahla’a District, Missan Governorate, IQ
Last Update: 07/10/2026
PetroChina International Iraq FZE Iraq Branch is a body registered in the Republic of Iraq to conduct the Petroleum Operations on behalf of a consortium of PetroChina International Iraq FZE, Petronas Carigali Iraq Holding B.V., Total E&P Iraq and South Oil Company of th...

Halliburton
3000 N. Sam Houston Pkwy E., Houston, 77032, US
Last Update: 06/09/2026
We collaborate and engineer solutions to maximize asset value for our customers. Founded in 1919, Halliburton is one of the world's largest providers of products and services to the energy industry. With more than 45,000 employees, representing 130 nationalities in more...
Compliance Ranges Comparison

PetroChina International Iraq FZE Iraq Branch







Halliburton






Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for PetroChina International Iraq FZE Iraq Branch in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Halliburton in 2026.
Incident History - PetroChina International Iraq FZE Iraq Branch (X = Date, Y = Severity)
PetroChina International Iraq FZE Iraq Branch cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Halliburton (X = Date, Y = Severity)
Halliburton cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

PetroChina International Iraq FZE Iraq Branch

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