CVE-2025-33108
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 Backup, Recovery and Media Services for i 7.4 and 7.5 could allow a user with the capability to compile or restore a program to gain elevated privileges due to a library unqualified call made by a BRMS program. A malicious actor could cause user-controlled code to run with component access to the host operating system.
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 · moderate confidenceIBM BRMS 7.4 and 7.5 contain a privilege escalation vulnerability where a BRMS program makes an unqualified library call, allowing a user with compilation or program restoration capabilities to inject and execute arbitrary code with elevated component-level access to the host IBM i operating system.
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.4= 7.5CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 installed BRMS versionUse the command DSPSFWRSC on IBM i and look for entry 'IBM Backup Recovery and Media Services for IBM i' (BRMS) and note the version number listed (7.4 or 7.5)Affected if BRMS version 7.4 or 7.5 is installed
-
Identify users with compilation authorityQuery the BRMS authority list or security authorities. On IBM i, use WRKAUT or check user profiles for *ALLOBJ or BRMS-specific compilation authorities (SPCMSPL) that grant compile capabilitiesAffected if Any user profile has BRMS compilation or compile-related authorities
-
Identify users with program restore capabilitiesReview user profiles with restore authority (*RST) or BRMS-specific program restoration capabilities. Use WRKUSRPRF and examine authorities for program restore functionsAffected if Any user profile has program restore or restoration authorities enabled
-
Confirm BRMS is actively configuredCheck if BRMS product is licensed (GO BRMS menu option) and if BRMS control language programs and libraries are present on the system. Verify BRMS is operational rather than just installedAffected if BRMS is licensed and actively configured for use
System is affected if BRMS version 7.4 or 7.5 is installed with any user accounts granted compilation or program restoration capabilities, allowing potential privilege escalation through the unqualified library call vulnerability.
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 dataApply IBM's security patch for BRMS 7.4 and 7.5; temporarily restrict or audit users granted compile and program restore capabilities until the patch is deployed.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-33108 — 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-33108 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