CVE-2023-4664
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 · uneditedIncorrect Default Permissions vulnerability in Saphira Saphira Connect allows Privilege Escalation. This issue affects Saphira Connect: before 9.
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 default permissions misconfiguration in Saphira Connect versions prior to version 9 allows local users to elevate privileges, likely due to overly permissive file or directory permissions that grant unintended access to sensitive resources or functionality.
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.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 Adobe Connect installation and versionLocate the Adobe Connect installation directory and find version information, typically in the application or configuration files, or check the installed programs list on the systemAffected if The installed version is less than 9.0 (e.g., 8.x, 7.x, etc.)
-
Examine installation directory permissionsReview file system permissions on the Adobe Connect installation folder and subdirectories, looking for permissions that allow unauthorized users or groups read, write, or execute accessAffected if Non-admin users or unnecessary groups have write or modify access to application directories, configuration files, or executable locations
-
Check configuration directory access controlsInspect permissions on configuration, logs, and data directories within the Adobe Connect installation, verifying that only authorized service accounts have accessAffected if Configuration files or sensitive directories are readable or writable by standard users or the Everyone group
-
Verify executable folder integrityExamine permissions on directories containing executable files (.exe, .dll, .bat, etc.) to ensure only administrators or the service account can modify themAffected if Standard users can modify or replace executable files in the application path
A user is affected if Adobe Connect version less than 9.0 is installed AND the installation directories have overly permissive file system permissions allowing non-adminstrative users access to sensitive resources.
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.0
Update Saphira Connect to version 9 or later to obtain corrected default permission configurations; review and harden file system permissions on affected installations.
Saphira Connect version 9.0
- 1. Identify current installed version of Saphira Connect
- 2. Review current system configuration and user accounts for any unauthorized privilege escalation
- 3. Obtain Saphira Connect version 9.0 from official vendor channels
- 4. Backup current configuration and data
- 5. Apply upgrade to Saphira Connect version 9.0
- 6. Verify the upgrade was successful and permissions are correctly configured
- 7. Test that privilege escalation vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4664 — 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-4664 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