Assets Discovery CloudApplication · Atlassian
CVE-2023-22523
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 · uneditedThis vulnerability, if exploited, allows an attacker to perform privileged RCE (Remote Code Execution) on machines with the Assets Discovery agent installed. The vulnerability exists between the Assets Discovery application (formerly known as Insight Discovery) and the Assets Discovery agent.
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 confidenceA remote code execution vulnerability exists in the communication pathway between Atlassian's Assets Discovery application (formerly Insight Discovery) and its deployed Assets Discovery agent. The flaw allows an authenticated attacker with network access to the agent to execute arbitrary code with elevated privileges on machines where the agent is installed.
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 CloudApplication
>= 1.0.0, < 3.2.0
Assets Discovery Data CenterApplication
>= 1.0.0, <= 3.1.11>= 6.0.0, < 6.2.0
Assets Discovery Data ServerApplication
>= 1.0.0, <= 3.1.11>= 6.0.0, < 6.2.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
- 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.
-
Identify if Assets Discovery is installedCheck for Atlassian Assets Discovery (formerly Insight Discovery) installation in your environment. For Data Center/Data Server, inspect the application management console or installed packages for Assets Discovery components.Affected if Assets Discovery Cloud, Data Center, or Data Server is present in the environment
-
Determine installed version of Assets Discovery CloudIn the Atlassian Cloud admin interface, navigate to Assets Discovery settings and locate the version information displayed in the product UI or about section.Affected if Version is >= 1.0.0 and < 3.2.0
-
Determine installed version of Assets Discovery Data Center or Data ServerCheck the installed application version through the Data Center administration console, or inspect the WAR/binary files, or run the product version command if available in the installation directory.Affected if Version is >= 1.0.0 and <= 3.1.11, or >= 6.0.0 and < 6.2.0
-
Verify network accessibility of Assets Discovery agentIdentify the network port used by the Assets Discovery agent (typically configurable during agent setup). Use network scanning tools or inspect firewall rules to determine if the agent port is exposed to untrusted networks or the internet.Affected if The agent communication port is accessible from untrusted network segments or external IP addresses
-
Check agent authentication configurationReview the Assets Discovery agent configuration files or settings to confirm whether authentication credentials are properly configured and enforced for the communication channel between the main application and the agent.Affected if Agent is configured to allow unauthenticated or weakly authenticated connections from the application to the agent
You are affected if Assets Discovery is installed with a version in the vulnerable ranges AND the agent communication channel is network-accessible to an authenticated attacker.
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.
dbcve · scoped3.2.06.2.0
Organizations should immediately restrict network access to the Assets Discovery agent communication channels, apply any available vendor patches, and verify agent configurations to prevent unauthorized privileged access.
Assets Discovery Cloud: >= 3.2.0 | Assets Discovery Data Center/Server: >= 3.2.0 (for 3.x) or >= 6.2.0 (for 6.x)
- Identify which Assets Discovery product you are running (Cloud, Data Center, or Data Server)
- Identify your current version using the product's admin interface or version command
- For Assets Discovery Cloud: Upgrade to version 3.2.0 or later
- For Assets Discovery Data Center/Server running version 3.x: Upgrade to version 3.2.0 or later
- For Assets Discovery Data Center/Server running version 6.x: Upgrade to version 6.2.0 or later
- After upgrade, verify the new version is running and the Assets Discovery agent is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Assets Discovery Cloud
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22523 — 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-2023-22523 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