VulnerabilityPublished 11 Nov 2025Updated 12 Nov 2025

CVE-2025-24847: Intel(R) CIP software · Information Disclosure

Affects Intel(R) CIP softwareSource CVE Database V5

Not known to be exploited · CVSS 5.7 Medium : upgrade to 2.4.0.11001 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

5.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.4.0.11001

CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: High
User Interaction: Passive
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Intel(R) CIP software to 2.4.0.11001.

Affected software

Product	Affected	Fixed in
Intel(R) CIP software	Affected <2.4.0.11001	Fixed in 2.4.0.11001

AI-suggested

Until then, implement strict network segmentation and access controls to limit exposure of systems running vulnerable versions, especially restricting network access to trusted entities only. Monitor privileged user accounts for unusual activity and enforce the principle of least privilege to reduce the risk of combined privileged/unprivileged exploitation scenarios. Employ network intrusion detection systems (IDS) and anomaly detection to identify potential exploitation attempts. Conduct regular audits of software versions and configurations to ensure no outdated Intel CIP software remains in production. Additionally, implement strong endpoint security controls to prevent unprivileged software from running unauthorized code alongside privileged user sessions. Educate privileged users about the risks and encourage prompt reporting of suspicious activity. Finally, maintain comprehensive logging and incident response plans tailored to information disclosure incidents.

Description

Improper input validation for some Intel(R) CIP software before version WIN_DCA_2.4.0.11001 within Ring 3: User Applications may allow an information disclosure. Unprivileged software adversary with a privileged user combined with a low complexity attack may enable data exposure. This result may potentially occur via network access when attack requirements are present without special internal knowledge and requires passive user interaction. The potential vulnerability may impact the confidentiality (high), integrity (none) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

Impact

For European organizations, this vulnerability poses a moderate risk primarily to confidentiality of sensitive data processed or stored by Intel(R) CIP software. Since the vulnerability can be exploited remotely over the network with low complexity, attackers could potentially extract sensitive information without disrupting system operations. This could lead to exposure of intellectual property, personal data, or other confidential information, which may have regulatory implications under GDPR and other data protection laws. The lack of impact on integrity and availability reduces the risk of operational disruption or data tampering but does not eliminate the risk of reputational damage or compliance penalties. Organizations relying on Intel CIP software in critical infrastructure, manufacturing, or data processing environments should be particularly vigilant. The requirement for a privileged user context combined with unprivileged software presence suggests that insider threats or compromised privileged accounts could facilitate exploitation. The passive user interaction requirement means that social engineering is not necessary, increasing the attack surface. Overall, the vulnerability could be leveraged in targeted attacks against European enterprises handling sensitive or regulated data.

References

intel.com/content/www/us/en/security-center/advisory/intel-sa-01328.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Nov 2025, 17:17 UTC

Technical details

References

Community reviews

Related threats