Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.90% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2023
CVE-2023-6378High confidence
Logback "receiver" DOS vulnerability
QOS.CH Sarl · logback
7.1HighCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs QOS.CH Sarl logback and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
- Debian Security Tracker: 1 affected package state with no published fix
Distribution package intelligence
4 package statesRelease-specific package status
Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | logback | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:1.2.11-5 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | logback | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | logback | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:1.2.11-5 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | logback | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:1.2.11-5 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
Open-source package ranges12 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Mavench.qos.logback:logback-classic | ECOSYSTEM: introduced 1.3.0; fixed 1.3.12 | 1.3.12 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavench.qos.logback:logback-classic | ECOSYSTEM: introduced 1.4.0; fixed 1.4.12 | 1.4.12 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavench.qos.logback:logback-classic | ECOSYSTEM: introduced 0; fixed 1.2.13 | 1.2.13 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavench.qos.logback:logback-core | ECOSYSTEM: introduced 1.3.0; fixed 1.3.12 | 1.3.12 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavench.qos.logback:logback-core | ECOSYSTEM: introduced 1.4.0; fixed 1.4.12 | 1.4.12 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavench.qos.logback:logback-core | ECOSYSTEM: introduced 0; fixed 1.2.13 | 1.2.13 | OSV record ↗aggregator derived · 10 Sep 2026 |
| mavench.qos.logback:logback-classic | >= 1.4.0, < 1.4.12 | 1.4.12 | GitHub advisory ↗github reviewed aggregator · 29 Nov 2024 |
| mavench.qos.logback:logback-classic | >= 1.3.0, < 1.3.12 | 1.3.12 | GitHub advisory ↗github reviewed aggregator · 29 Nov 2024 |
| mavench.qos.logback:logback-classic | < 1.2.13 | 1.2.13 | GitHub advisory ↗github reviewed aggregator · 29 Nov 2024 |
| mavench.qos.logback:logback-core | >= 1.4.0, < 1.4.12 | 1.4.12 | GitHub advisory ↗github reviewed aggregator · 29 Nov 2024 |
| mavench.qos.logback:logback-core | >= 1.3.0, < 1.3.12 | 1.3.12 | GitHub advisory ↗github reviewed aggregator · 29 Nov 2024 |
| mavench.qos.logback:logback-core | < 1.2.13 | 1.2.13 | GitHub advisory ↗github reviewed aggregator · 29 Nov 2024 |
Direct vendor intelligence
2 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2023-6378 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitylogback: serialization vulnerability in logback receiver
The vendor explicitly identifies these products as affected by this CVE.
- logback.src as a component of Migration Toolkit for Applications 6
- logback.src as a component of Migration Toolkit for Applications 7
- logback as a component of OpenShift Serverless
- logback as a component of Red Hat build of Apache Camel for Spring Boot 3
- logback as a component of Red Hat build of Debezium 2
- logback as a component of Red Hat build of OptaPlanner 8
- logback as a component of Red Hat Data Grid 8
- logback as a component of Red Hat Decision Manager 7
- logback as a component of Red Hat Integration Camel K 1
- logback as a component of Red Hat JBoss Data Grid 7
- logback as a component of Red Hat JBoss Enterprise Application Platform 6
- org.keycloak-keycloak-parent as a component of Red Hat JBoss Enterprise Application Platform 6
- Summary
- A flaw was found in the logback package, where it is vulnerable to a denial of service caused by a serialization flaw in the receiver component. By sending specially crafted poisoned data, a remote attacker can cause a denial of service condition.
- Remediation
- Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
SSA-784301 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-784301: Multiple Vulnerabilities in SINEC NMS Before V3.0
The vendor explicitly identifies these products as affected by this CVE.
- SINEC NMS
- Summary
- A serialization vulnerability in logback receiver component part of logback version 1.4.11 allows an attacker to mount a Denial-Of-Service attack by sending poisoned data.
- Remediation
- Update to V3.0 or later version
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
A serialization vulnerability in logback receiver component part of logback version 1.4.11 allows an attacker to mount a Denial-Of-Service attack by sending poisoned data.
What
A serialization vulnerability in logback receiver component part of logback version 1.4.11 allows an attacker to mount a Denial-Of-Service attack by sending poisoned data.
Why
Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.
How
An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
A serialization vulnerability in logback receiver component part of logback version 1.4.11 allows an attacker to mount a Denial-Of-Service attack by sending poisoned data.
Why
Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.
How
An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Deserialization of Untrusted Data → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Changed: exploitation can affect a different security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-502 ↗
CWE-502: Deserialization of Untrusted Data. The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- logback.src as a component of Migration Toolkit for Applications 6
- logback.src as a component of Migration Toolkit for Applications 7
- logback as a component of OpenShift Serverless
- logback as a component of Red Hat build of Apache Camel for Spring Boot 3
- logback as a component of Red Hat build of Debezium 2
- logback as a component of Red Hat build of OptaPlanner 8
- logback as a component of Red Hat Data Grid 8
- logback as a component of Red Hat Decision Manager 7
- logback as a component of Red Hat Integration Camel K 1
- logback as a component of Red Hat JBoss Data Grid 7
- logback as a component of Red Hat JBoss Enterprise Application Platform 6
- org.keycloak-keycloak-parent as a component of Red Hat JBoss Enterprise Application Platform 6
- logback as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack
- logback as a component of Red Hat Process Automation 7
- logback as a component of Red Hat Single Sign-On 7
- logback as a component of streams for Apache Kafka
- Fixed
- devspaces/server-rhel8@sha256:3be3bc2226f6719f8227709ea13626bee7135d1dc0d64aa4d8ee4ef6e8bb60df_s390x as a component of Red Hat OpenShift Dev Spaces 3
- devspaces/server-rhel8@sha256:b6912aa0c1717be5d0e69c31e94e834abe1307d5e8132345af89a923d5b687ce_amd64 as a component of Red Hat OpenShift Dev Spaces 3
- devspaces/server-rhel8@sha256:d0ae2f24410876f45670107480e10d98b59e08cac3561095f86dfdda1d759b78_ppc64le as a component of Red Hat OpenShift Dev Spaces 3
- RHINT Camel-Springboot 4.0.3
- Red Hat AMQ Broker 7
- Red Hat Fuse 7.13.0
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 29 Nov 2023 · Last source change 29 Nov 2024, 12:04 UTC · CWE-502 · Deserialization of Untrusted Data
CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2023-3046
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.