CVE-2025-0799
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 App Connect enterprise 12.0.1.0 through 12.0.12.10 and 13.0.1.0 through 13.0.2.1 could allow an authenticated user to write to an arbitrary file on the system during bar configuration deployment due to improper pathname limitations on restricted directories.
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 App Connect Enterprise versions 12.0.1.0-12.0.12.10 and 13.0.1.0-13.0.2.1 contain a path traversal vulnerability during BAR (Broker Archive) configuration deployment. Authenticated users with deployment privileges can write to arbitrary filesystem locations outside intended directories due to insufficient pathname validation, potentially enabling privilege escalation or code execution.
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>= 12.0.1.0, <= 12.0.12.10>= 13.0.1.0, <= 13.0.2.1CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Identify installed IBM App Connect Enterprise versionRun the IBM command to display the product version (for example, mqsireportproperties or the appropriate IBM utility for your installation). Compare the reported version number against the affected ranges: 12.0.1.0 through 12.0.12.10, and 13.0.1.0 through 13.0.2.1.Affected if The installed version falls within either of the two affected ranges.
-
Confirm BAR deployment functionality is accessibleReview the IBM App Connect Enterprise configuration to determine whether BAR (Broker Archive) file deployment is enabled and accessible to users. Check the deployment-related settings in the integration node or integration server configuration.Affected if BAR deployment is enabled and available to users in your environment.
-
Review user deployment privilegesExamine the role-based access control (RBAC) or permission settings for BAR deployment. Identify which users or groups have the ability to deploy BAR files. Determine if any users without full administrator privileges retain deployment capabilities.Affected if Users other than fully trusted administrators have been granted deployment privileges.
-
Inspect deployment audit and trace logsLocate and review the BAR deployment audit logs or trace files for your integration node. Look for deployment operations that occurred outside expected patterns, particularly those involving unusual target paths.Affected if Deployment records show operations targeting unexpected filesystem locations.
-
Scan for unexpected files in system directoriesExamine the filesystem directories where BAR deployments are intended to extract files. Compare against expected deployment contents to identify any files written outside the designated directories.Affected if Files exist in locations outside the intended BAR deployment target directories.
Your environment is affected if the installed version is within 12.0.1.0-12.0.12.10 or 13.0.1.0-13.0.2.1 AND BAR deployment is accessible to users beyond trusted administrators.
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 (12.0.12.11+ or 13.0.2.2+) to address improper pathname validation. Prior to patching, strictly limit BAR deployment permissions to trusted administrators only and audit deployment activities for signs of exploitation.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0799 — 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-0799 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