dbcve.org
Vuforia StudioApplication · Ptc

CVE-2023-29152

HIGH · 8.1 CVSS v3.1 Published 2023-06-07
Fix available
A fix is available. Upgrade to 9.9 or later.
See remediation →
87/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
By changing the filename parameter in the request, an attacker could delete any file with the permissions of the Vuforia server account.

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

Arbitrary file deletion vulnerability in PTC Vuforia where an attacker can manipulate the filename parameter in a request to delete any file accessible to the server's account permissions, likely due to insufficient path traversal validation on user-supplied input.

MitigationImplement strict input validation and sanitization on the filename parameter, use allowlists for permitted file operations, ensure the web server process runs with minimal file system privileges, and apply principle of least privilege to file deletion operations.

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
Vuforia StudioApplication
Affected:< 9.9

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Identify Vuforia Studio installation and version
    Locate the Vuforia Studio installation directory and check the version information file or product metadata. Common locations include program files or installation directories. Use product-specific commands or check version files in the installation path.
    Affected if The installed version is found to be below 9.9 (e.g., 9.8.x, 9.7.x, etc.)
  2. Confirm the web service is running
    Verify that the Vuforia Studio web service or application server is active and accessible. Check service status through system management tools or by attempting to access the web interface on the configured port.
    Affected if The web service is running and accepting requests, as the vulnerability is exploited via HTTP requests to the filename parameter
  3. Check if file operation endpoints are exposed
    Examine the web application's exposed endpoints or API routes related to file handling. Look for file deletion, file management, or upload functionality that accepts a filename parameter in the request.
    Affected if File deletion or management endpoints are accessible without additional authentication or with standard user credentials
  4. Inspect input validation configuration
    Review the application's configuration files or settings related to request parameter handling. Look for filename or file path parameters in the web request configuration to understand how user input is processed.
    Affected if The application accepts filename parameters without strict path traversal validation or allowlist enforcement

A user is affected if Vuforia Studio version is below 9.9 AND the web service with file operation functionality is accessible and processes filename parameters without proper path traversal protection.

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 9.9 or later
Fixed in 9.9
Interim mitigation

Implement strict input validation and sanitization on the filename parameter, use allowlists for permitted file operations, ensure the web server process runs with minimal file system privileges, and apply principle of least privilege to file deletion operations.

Recommended fix High confidence

Vuforia Studio 9.9

  1. Backup your current Vuforia Studio installation and all project data
  2. Download Vuforia Studio version 9.9 from the official PTC distribution portal or support site
  3. Follow the official Vuforia Studio upgrade documentation to install version 9.9
  4. After upgrade, verify the authorization fix is working by confirming that file deletion requests are properly validated against user permissions
  5. Test that users can only delete files they are authorized to access

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

Fix this in Vuforia Studio 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 the upgrade done

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-2023-29152 — 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-29152 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