dbcve.org
Management SuiteApplication · Baramundi

CVE-2022-43747

CRITICAL · 9.8 CVSS v3.1 Published 2022-10-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
baramundi Management Agent (bMA) in baramundi Management Suite (bMS) 2021 R1 and R2 and 2022 R1 allows remote code execution. This is fixed in security update S-2022-01, which contains fixed bMA setup files for these versions. This also is fixed in baramundi Management Suite 2022 R2.

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 confidence

The baramundi Management Agent (bMA) in baramundi Management Suite versions 2021 R1, R1 R2, and 2022 R1 contains a critical vulnerability allowing remote code execution. This vulnerability has a CVSS score of 9.8 indicating severe risk. The issue is addressed through security update S-2022-01 containing fixed bMA setup files, or by upgrading to version 2022 R2.

MitigationApply security update S-2022-01 to affected bMA installations in versions 2021 R1/R2 and 2022 R1, or upgrade to baramundi Management Suite 2022 R2 which contains the fix.

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
Management SuiteApplication
Affected:= 2021= 2022

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate baramundi Management Suite installation
    Search for the baramundi Management Suite installation directory, typically under Program Files or Program Files (x86), or check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'baramundi'
    Affected if The product is not found or no bMA component is installed, the system is not affected by this specific vulnerability
  2. Identify installed Management Suite version
    Open the baramundi Management Suite console and navigate to Help > About, or check the version information in the installed program files. The version is typically displayed as a four-part number like 2021.R1.x.x
    Affected if Version shows 2021 R1, 2021 R1 R2, or 2022 R1 - these versions contain the vulnerable bMA component
  3. Verify bMA component version
    In the Management Suite console, navigate to the bMA (Management Agent) section or check the bMA setup files in the installation directory. The bMA version should be listed in the agent properties or deployment settings
    Affected if bMA version corresponds to the affected Management Suite versions (2021 R1, R1 R2, or 2022 R1)
  4. Check if security update S-2022-01 was applied
    Examine the bMA setup files or check the Management Suite update history. The update S-2022-01 modifies the bMA setup files to the fixed version
    Affected if The bMA setup files have not been updated to the S-2022-01 fixed versions, meaning the vulnerability remains exploitable

A system is affected if baramundi Management Suite version 2021 R1, 2021 R1 R2, or 2022 R1 is installed with the bMA component and security update S-2022-01 has not been applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply security update S-2022-01 to affected bMA installations in versions 2021 R1/R2 and 2022 R1, or upgrade to baramundi Management Suite 2022 R2 which contains the fix.

Recommended fix High confidence

baramundi Management Suite 2022 R2

  1. Identify the current version of baramundi Management Suite (bMS) and baramundi Management Agent (bMA) in use
  2. Obtain the security update S-2022-01 from the official baramundi download portal, which contains fixed bMA setup files
  3. Apply the S-2022-01 security update to affected installations running 2021 R1, 2021 R2, or 2022 R1
  4. Alternatively, upgrade to baramundi Management Suite 2022 R2 which includes the security fix
  5. Verify that the bMA version has been updated and the security update is properly applied
  6. Confirm remote code execution vulnerability is mitigated by the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Management Suite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43747 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-43747 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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