CVE-2012-2166

Hard-coded Credentials in IBM XIV Storage System 2810-A14 and 2812-A14 devices before level 10

Verified by Precogs Threat Research
Last Updated: Nov 21, 2024
Base Score
9.8CRITICAL

Executive Summary

CVE-2012-2166 is a critical severity vulnerability affecting pii-secrets. It is classified as Hard-coded Credentials. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"Precogs PII & Secrets Scanner automatically identifies hardcoded credentials, exposed API keys, and personally identifiable information leaks across repositories, CI/CD pipelines, and deployed artifacts."

Exploit Probability (EPSS)
Low (3.0%)
Public POC
Available
Exploit Probability
High (84%)
Public POC
Available
Affected Assets
pii secretsCWE-798

What is this vulnerability?

CVE-2012-2166 is categorized as a critical Hard-coded Credentials flaw with a CVSS base score of 9.8. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

IBM XIV Storage System 2810-A14 and 2812-A14 devices before level 10.2.4.e-2 and 2810-114 and 2812-114 devices before level 11.1.1 have hardcoded passwords for unspecified accounts, which allows remote attackers to gain user access via unknown vectors. IBM X-Force ID: 75041.

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score9.8 (CRITICAL)
Vector StringCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
PublishedFebruary 8, 2018
Last ModifiedNovember 21, 2024
Related CWEsCWE-798

Impact on Systems

Credential Theft: Exposed secrets enable unauthorized access to infrastructure, cloud services, and third-party integrations.

Compliance Violation: Leaking PII or credentials may violate GDPR, HIPAA, PCI-DSS, and SOC 2 requirements.

Supply Chain Risk: Compromised credentials in public repositories can propagate to downstream consumers.

How to Fix and Mitigate CVE-2012-2166

  1. Apply Vendor Patches: Upgrade affected components to their latest, non-vulnerable versions immediately.
  2. Implement Input Validation: Ensure all user-supplied data is validated, sanitized, and type-checked before processing.
  3. Deploy Runtime Protection: Use Precogs continuous monitoring to detect exploitation attempts in real time.
  4. Audit Dependencies: Review and update all third-party libraries and transitive dependencies.

Defending with Precogs AI

Precogs PII & Secrets Scanner automatically identifies hardcoded credentials, exposed API keys, and personally identifiable information leaks across repositories, CI/CD pipelines, and deployed artifacts.

Use Precogs to continuously scan your codebase, binaries, APIs, and infrastructure for this vulnerability class and related attack patterns. Our AI-powered detection engine combines static analysis with threat intelligence to identify exploitable weaknesses before attackers do.

Start scanning with Precogs →

Vulnerability Code Signature

Attack Data Flow

StageDetail
SourceSource code repository
VectorSecrets embedded directly in the codebase
SinkAuthentication API or database connection
ImpactUnauthorized access, data breach

Vulnerable Code Pattern

// ❌ VULNERABLE: Hardcoded credential
public class DatabaseConfig {
    // Taint sink: secret embedded in code
    public static final String DB_PASSWORD = "SuperSecretPassword123!";
}

Secure Code Pattern

// ✅ SECURE: Environment variables
public class DatabaseConfig {
    // Sanitized configuration
    public static final String DB_PASSWORD = System.getenv("DB_PASSWORD");
}

How Precogs Detects This

Precogs PII & Secrets Scanner continuously monitors codebases for hardcoded secrets, API keys, and reversible encryption.

Related Vulnerabilitiesvia CWE-798

Is your system affected?

Precogs AI detects CVE-2012-2166 in compiled binaries, LLMs, and application layers — even without source code access.