CVE-2023-28317
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 · uneditedA vulnerability has been discovered in Rocket.Chat, where editing messages can change the original timestamp, causing the UI to display messages in an incorrect order.
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 confidenceRocket.Chat has a vulnerability where the message editing function allows users to modify the original timestamp of messages, causing the UI to display messages in incorrect chronological order. This is an integrity issue where the original message timestamp should remain immutable even after edits.
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 dataall versionsCVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Confirm Rocket.Chat is installedIdentify the Rocket.Chat deployment in your environment. This may be a Docker container, a systemd service, or running on a known host/port. Check for processes named 'rocket.chat' or 'node' serving Rocket.Chat on ports like 3000 or 443.Affected if Rocket.Chat is found in your environment
-
Identify the Rocket.Chat versionAccess the Rocket.Chat administration panel (typically at /admin/info) or run 'rocketchatctl version' if the CLI tool is available. Alternatively, check package.json or the installed node_modules for the Rocket.Chat version string.Affected if Any version of Rocket.Chat is confirmed to be running (all versions are affected)
-
Test message editing timestamp behaviorLog into Rocket.Chat as a regular user. Send a message and note the exact timestamp displayed. Wait at least one minute, then edit the message using the edit function (usually a pencil icon). After saving the edit, observe whether the displayed timestamp has changed to the current time or remains as the original timestamp.Affected if The message timestamp changes to the edit time or becomes editable, indicating the vulnerability is present
If Rocket.Chat is running and message edits cause the displayed timestamp to update to the current time rather than preserving the original timestamp, the environment is affected by CVE-2023-28317.
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.
From vendor dataApply the vendor patch for CVE-2023-28317 which enforces immutable original timestamps during message edits, ensuring chronological message order is preserved in the UI.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28317 — 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-28317 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