CVE-2024-1143
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 · uneditedCentral Dogma versions prior to 0.64.1 is vulnerable to Cross-Site Scripting (XSS), which could allow for the leakage of user sessions and subsequent authentication bypass.
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 confidenceCentral Dogma versions before 0.64.1 contain a stored XSS vulnerability that allows attackers to inject malicious scripts into the application, potentially stealing user session cookies or tokens and bypassing authentication mechanisms.
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< 0.64.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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.
-
Identify Central Dogma versionLocate the Central Dogma installation and check its version - this may be found in the JAR file name, docker image tag, service manifest, or by querying the application API if a version endpoint existsAffected if The installed version is any release before 0.64.1 (e.g., 0.64.0, 0.63.0, 0.60.0, etc.)
-
Confirm application is reachableVerify that the Central Dogma web interface or API is accessible - this can be done by checking if the service is listening on its configured HTTP portAffected if The application is running and accessible to users or attackers
-
Identify user input entry pointsReview the Central Dogma configuration and application to determine what features accept user-supplied content - this typically includes project names, repository descriptions, issue tracker fields, or any text input stored by the applicationAffected if Any feature that stores and displays user-provided text back to users or administrators is enabled and in use
-
Check for suspicious stored contentInspect stored data in the application's database or repository for any unexpected script tags, JavaScript event handlers, or encoded payloads that could indicate exploitation (e.g., <script>, javascript:, onerror=, onload=)Affected if Any such payloads are found stored in the application's data stores
You are affected if Central Dogma version is below 0.64.1 AND the application accepts and displays user input through its web interface or API.
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 · scoped0.64.1
Upgrade Central Dogma to version 0.64.1 or later to obtain the security patch. If immediate upgrade is not possible, implement input validation and output encoding on all user-supplied content.
0.64.1
- Identify the current installed version of Central Dogma by checking the application's build configuration or running version command
- Stop the Central Dogma service to prevent any active sessions during upgrade
- Backup the existing Central Dogma installation directory and configuration files
- Download Central Dogma version 0.64.1 from the official GitHub releases repository
- Replace the existing Central Dogma binaries with the version 0.64.1 binaries
- Verify the integrity of the downloaded package using checksums if available
- Review and update any custom configurations if needed to match the new version requirements
- Start the Central Dogma service and verify it runs without errors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.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,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1143 — 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-2024-1143 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