dbcve.org
Assets Discovery Data CenterApplication · Atlassian

CVE-2024-21682

HIGH · 7.2 CVSS v3.1 Published 2024-02-20
Fix available
A fix is available. Upgrade to 6.2.1 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
This High severity Injection vulnerability was introduced in Assets Discovery 1.0 - 6.2.0 (all versions). Assets Discovery, which can be downloaded via Atlassian Marketplace, is a network scanning tool that can be used with or without an agent with Jira Service Management Cloud, Data Center or Server. It detects hardware and software that is connected to your local network and extracts detailed information about each asset. This data can then be imported into Assets in Jira Service Management to help you manage all of the devices and configuration items within your local network. This Injection vulnerability, with a CVSS Score of 7.2, allows an authenticated attacker to modify the actions taken by a system call which has high impact to confidentiality, high impact to integrity, high impact to availability, and requires no user interaction. Atlassian recommends that Assets Discovery customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions See the release notes (https://confluence.atlassian.com/assetapps/assets-discovery-3-2-1-cloud-6-2-1-data_center-1333987182.html). You can download the latest version of Assets Discovery from the Atlassian Marketplace (https://marketplace.atlassian.com/apps/1214668/assets-discovery?hosting=datacenter&tab=installation). This vulnerability was reported via our Penetration Testing program.

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 confidence

An Injection vulnerability in Atlassian Assets Discovery versions 1.0-6.2.0 allows an authenticated attacker to modify the actions taken by a system call, resulting in high impact to confidentiality, integrity, and availability.

MitigationUpgrade Assets Discovery to the latest version or one of the supported fixed versions as specified in the Atlassian release notes.

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
Assets Discovery Data CenterApplication
Affected:>= 1.0.0, < 6.2.1

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm Atlassian Assets Discovery installation
    Locate the Atlassian Assets Discovery application in your environment - typically found via the Atlassian admin console, installed applications list, or system inventory
    Affected if The product is not installed, this CVE does not apply
  2. Identify installed version
    Access the Atlassian admin console or check the application metadata file (typically version.info or similar) within the Assets Discovery installation directory
    Affected if Unable to determine the version number - manual verification may be required
  3. Check if Data Center edition
    Verify the deployment type through the Atlassian admin console or installation documentation - confirm it is the Data Center variant
    Affected if Only the Data Center edition is listed as affected; Server/Cloud variants have separate tracking
  4. Compare version against vulnerable range
    Compare your installed version to the affected range: versions 1.0.0 through 6.2.0 are vulnerable; version 6.2.1 and later are fixed
    Affected if Installed version is 1.0.0 or higher but lower than 6.2.1 - this indicates the environment is affected by the injection vulnerability

Your environment is affected if Atlassian Assets Discovery Data Center is installed with a version between 1.0.0 and 6.2.0 inclusive; versions 6.2.1 and later are not vulnerable

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
Upgrade available Upgrade to 6.2.1 or later
Fixed in 6.2.1
Interim mitigation

Upgrade Assets Discovery to the latest version or one of the supported fixed versions as specified in the Atlassian release notes.

Recommended fix High confidence

Assets Discovery 6.2.1 or later (Data Center)

  1. Confirm current Assets Discovery version by navigating to the Atlassian admin console or checking the installed application version
  2. Review the Assets Discovery release notes at https://confluence.atlassian.com/assetapps/assets-discovery-3-2-1-cloud-6-2-1-data_center-1333987182.html for upgrade prerequisites
  3. Create a backup of the current Assets Discovery configuration and any collected data
  4. Download Assets Discovery version 6.2.1 or later from the Atlassian Marketplace at https://marketplace.atlassian.com/apps/1214668/assets-discovery?hosting=datacenter&tab=installation
  5. Follow Atlassian's standard upgrade procedure for Data Center applications to install the new version
  6. Verify the upgrade was successful by checking the installed version in the admin console
  7. Validate that Assets Discovery functionality remains operational post-upgrade
Caveat Review release notes for any configuration or behavioral changes between your current version and 6.2.1; test in a non-production environment before deploying to production

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

Fix this in Assets Discovery Data Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21682 — 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-2024-21682 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