dbcve.org
InsightappsecApplication · Rapid7

CVE-2023-1305

HIGH · 8.1 CVSS v3.1 Published 2023-03-21
Fix available
A fix is available. Upgrade to 23.2.1 / 2023.02.01 or later.
See remediation →
87/100
Remediation priority · High
Public exploit 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
An authenticated attacker can leverage an exposed “box” object to read and write arbitrary files from disk, provided those files can be parsed as yaml or JSON. This issue was resolved in the Managed and SaaS deployments on February 1, 2023, and in version 23.2.1 of the Self-Managed version of InsightCloudSec.

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

A detailed technical summary for this CVE is being prepared.

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
InsightappsecApplication
Affected:< 23.2.1
InsightcloudsecApplication
Affected:< 2023.02.01

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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 23.2.1 / 2023.02.01 or later
Fixed in 23.2.12023.02.01
Recommended fix High confidence

InsightAppSec Self-Managed: upgrade to version 23.2.1 or later | InsightCloudSec Self-Managed: upgrade to 2023.02.01 (February 2023 release) or later | Managed/SaaS: fix applied on February 1, 2023

  1. 1. Identify which Insight product(s) are deployed in your environment: InsightAppSec (application security testing) or InsightCloudSec (cloud security platform).
  2. 2. For InsightAppSec Self-Managed deployments: Check current version by navigating to the admin console or running: `insight-appsec version`
  3. 3. If version is below 23.2.1, plan upgrade to version 23.2.1 or later. Review upgrade documentation at docs.divvycloud.com for version-specific upgrade procedures.
  4. 4. For InsightCloudSec Self-Managed deployments: Check current version in the platform settings.
  5. 5. If version is below 2023.02.01, upgrade to the February 2023 release (2023.02.01) or later.
  6. 6. For Managed/SaaS deployments: No action required as the fix was applied on February 1, 2023. Verify with your Tenable/divvy support representative if needed.
  7. 7. After upgrade, verify the 'box' object exposure is remediated by confirming the patched version is running.

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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