CVE-2025-33119
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM QRadar SIEM 7.5 through 7.5.0 UP14 stores user credentials in configuration files in source control which can be read by an authenticated user.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIBM QRadar SIEM 7.5 through 7.5.0 UP14 contains a vulnerability where user credentials are stored in plaintext within configuration files that are committed to source control repositories. Any authenticated user with access to the source control system can read these stored credentials, leading to potential account compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify QRadar SIEM versionRun the command to display the installed QRadar version (typically via the admin console or CLI command such as 'qradar_version' or checking /opt/qradar/version file). Compare the output to the affected range: 7.5.0 through 7.5.0 UP14.Affected if The installed version falls within 7.5.0 through 7.5.0 UP14.
-
Identify configuration files in source controlReview all configuration files that have been committed to the source control repositories used in your QRadar deployment. Search for files with extensions such as .conf, .xml, .properties, .json, .yaml, .yml, .ini, or .cfg that are stored in the repository.Affected if Configuration files containing user credentials are present in the source control repository.
-
Search for plaintext credentials in config filesExamine the contents of configuration files for patterns indicating plaintext credentials such as 'password=', 'username=', 'credential=', 'secret=', 'api_key=', 'auth_token=', or similar key-value pairs storing sensitive authentication data in unencrypted form.Affected if Any configuration file contains plaintext passwords, usernames, API keys, tokens, or other credentials.
-
Audit source control historyReview the commit history and diffs of the source control repository to identify any past commits that introduced credentials into configuration files. Use commands like 'git log', 'git diff', or repository browsing tools to examine historical versions.Affected if Historical commits reveal that credentials were ever stored in plaintext within configuration files committed to source control.
A user is affected if their QRadar SIEM version is 7.5.0 through 7.5.0 UP14 AND any configuration files containing plaintext credentials exist in or have been committed to their source control repository.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemove hardcoded credentials from configuration files and implement proper secrets management (e.g., credential vault, environment variables, or secrets management services). Rotate any exposed credentials immediately and audit source control history for credential exposure.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-33119 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-33119 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data