CVE-2023-29168
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 · uneditedThe local Vuforia web application does not support HTTPS, and federated credentials are passed via basic authentication.
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 confidenceThe local Vuforia web application does not use HTTPS encryption, and federated credentials are transmitted using basic authentication, which encodes (not encrypts) credentials in base64. This exposes credentials and application data in cleartext over the network, allowing interception via man-in-the-middle attacks.
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< 9.9CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify if HTTPS is enabled on the Vuforia web applicationInspect the web server configuration for Vuforia Studio and check whether SSL/TLS is configured and enforced. Look for HTTP vs HTTPS bindings in the web server settings.Affected if The Vuforia web application is accessible over HTTP (port 80) without redirect to HTTPS, or HTTPS is not configured at all.
-
Identify the authentication mechanism in useReview the authentication configuration settings within Vuforia Studio. Check whether basic authentication (username/password sent as base64-encoded header) is enabled or required.Affected if Basic authentication is enabled or required for the Vuforia web application.
-
Capture network traffic to observe credential transmissionUse a network capture tool (such as Wireshark or tcpdump) to capture traffic between the client and the Vuforia web application during login. Examine the headers to see if credentials are sent in base64 encoding within the Authorization header.Affected if Credentials are transmitted in the HTTP Authorization header using the Basic scheme (base64-encoded) rather than being encrypted via TLS or replaced with OAuth/OIDC.
-
Check if HTTPS is enforced for all connectionsVerify whether the web server rejects HTTP connections or forces redirect to HTTPS. Also check if HSTS (HTTP Strict Transport Security) headers are configured.Affected if HTTP connections are accepted without redirect to HTTPS, or HTTPS is optional rather than mandatory.
-
Confirm the installed Vuforia Studio versionCheck the installed version of PTC Vuforia Studio in the system information or about dialog.Affected if The installed version is lower than 9.9 (e.g., 9.8, 9.7, earlier versions).
You are affected if Vuforia Studio version is below 9.9 AND the web application is accessible over HTTP or uses basic authentication for credential transmission without HTTPS enforcement.
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 · scoped9.9
Enable HTTPS on the Vuforia web application with valid TLS certificates and replace basic authentication with a secure authentication protocol such as OAuth 2.0 or OIDC to properly protect credential transmission.
Vuforia Studio 9.9 or later
- Upgrade Vuforia Studio to version 9.9 or later to obtain HTTPS support
- After upgrading, verify that HTTPS is enabled and properly configured for the Vuforia web application
- Ensure that all federated credentials now use secure authentication mechanisms rather than basic authentication over HTTP
- Test the upgrade in a staging environment before deploying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing3.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 $4,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29168 — 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-29168 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