Vulnerability in com.linecorp.centraldogma:centraldogma-serv… (CVE-2024-1143)

Summary

Vulnerability in com.linecorp.centraldogma:centraldogma-server (CVE-2024-1143). Confidential information can be exposed externally. Mitigation: upgrade to 0.64.1 or later.

Original description

The description as published by the source.

Vulnerability Overview

A vulnerability has been identified in Central Dogma versions prior to 0.64.1, allowing for the leakage of user sessions and subsequent authentication bypass. The issue stems from a Cross-Site Scripting (XSS) attack vector that targets the RelayState of Security Assertion Markup Language (SAML).

Impact

Successful exploitation of this vulnerability enables malicious actors to leak user sessions, leading to the compromise of authentication mechanisms. This, in turn, can facilitate unauthorized access to sensitive resources.

Patches

This vulnerability is addressed and resolved in Central Dogma version 0.64.1 Users are strongly encouraged to upgrade to this version or later to mitigate the risk associated with the authentication bypass.

Workarounds

No viable workarounds are currently available for this vulnerability. It is recommended to apply the provided patch promptly.

References

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-1143 has been found in com.linecorp.centraldogma:centraldogma-server.
Confidential information can be exposed externally.
What to do: upgrade com.linecorp.centraldogma:centraldogma-server to 0.64.1 or later.
If unsure, ask your IT team or search "com.linecorp.centraldogma:centraldogma-server CVE-2024-1143" on the vendor's site.

CVE-2024-1143 (com.linecorp.centraldogma:centraldogma-server)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.64.1 — apply immediately
Workaround: No viable workarounds are currently available for this vulnerability.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in com.linecorp.centraldogma:centraldogma-server.

📍 Affected scope

Check the vendor advisory for the affected versions of com.linecorp.centraldogma:centraldogma-server.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 0.64.1.

🛡️ Workaround

Workaround: No viable workarounds are currently available for this vulnerability.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで com.linecorp.centraldogma:centraldogma-server を使っているサービスとバージョンを洗い出す。
2
Apply temporary workaround mitigate
```
No viable workarounds are currently available for this vulnerability.
```
パッチが適用されるまでの応急処置として、No viable workarounds are currently available for this vulnerability. を実施。回避策の副作用 (機能低下) を確認した上で。
3
Apply patch patch
```
Upgrade com.linecorp.centraldogma:centraldogma-server to 0.64.1
```
ステージング環境で 0.64.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
4
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven com.linecorp.centraldogma:centraldogma-server

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.64.1"}]}]

References

advisory nvd.nist.gov
package github.com
web github.com
web github.com