CVE-2023-46327
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 · uneditedMultiple MFPs (multifunction printers) provided by FUJIFILM Business Innovation Corp. and Xerox Corporation provide a facility to export the contents of their Address Book with encrypted form, but the encryption strength is insufficient. With the knowledge of the encryption process and the encryption key, the information such as the server credentials may be obtained from the exported Address Book data. As for the details of affected product names, model numbers, and versions, refer to the information provided by the respective vendors listed under [References].
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 confidenceFujifilm Business Innovation and Xerox MFPs use weak encryption when exporting Address Book data. An attacker with knowledge of the encryption algorithm and key can decrypt exported Address Book files to extract stored server credentials. The vulnerability stems from insufficient cryptographic strength in the export encryption mechanism.
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< 85.40.31< 85.40.31< 90.40.91< 90.40.91< 90.40.91< 90.40.91< 68.81.41< 68.81.41CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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.
-
Check installed firmware versionAccess the device control panel or web interface and navigate to System Settings or Device Information to view the current firmware version. Compare against the affected version thresholds: C9065/C9070 need 85.40.31 or higher; B9136/B9125/B9110/B9100 need 90.40.91 or higher; Versalink C405/C505 need 68.81.41 or higher.Affected if The installed firmware version is lower than the specified threshold for your model.
-
Identify Address Book export usageReview system audit logs or administrator records to determine if the Address Book export function has been used. Look for export events or check if exported .csv or .xml files exist on connected systems or network shares.Affected if Address Book data has been exported from the device.
-
Verify Address Book contentsAccess the Address Book or Directory settings via the device web interface and review stored contacts. Check for entries that contain server credentials such as SMTP authentication, LDAP bind passwords, SharePoint credentials, or other authentication data.Affected if The Address Book contains server authentication credentials.
-
Assess network exposureDetermine if the MFP web interface and export functions are accessible from untrusted networks. Review firewall rules and access control lists restricting administrative functions.Affected if The device administrative interface is accessible from untrusted or public networks.
You are affected if your device firmware is below the specified version threshold AND the Address Book has been exported while containing server credentials, creating a risk that exported files could be decrypted by an 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 · scoped68.81.4185.40.3190.40.91
Apply vendor-supplied firmware updates when available. Until then, avoid exporting Address Book data containing sensitive credentials, or restrict access to the export function to trusted administrators only.
Primelink C9065/C9070: firmware 85.40.31+; Primelink B9136/B9125/B9110/B9100: firmware 90.40.91+; Versalink C405/C505: firmware 68.81.41+
- 1. Identify the exact model number and current firmware version of the affected device
- 2. Navigate to the vendor's official support website (Fujifilm Business Innovation or Xerox depending on model)
- 3. Locate the firmware download section for the specific model
- 4. Download the firmware version 85.40.31 or higher for Primelink C9065/C9070
- 5. Download the firmware version 90.40.91 or higher for Primelink B9136/B9125/B9110/B9100
- 6. Download the firmware version 68.81.41 or higher for Versalink C405/C505
- 7. Access the device administration web interface or control panel
- 8. Navigate to the firmware update/maintenance section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46327 — 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-46327 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