BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2023-53222High confidence

jfs: jfs_dmap: Validate db_l2nbperpage while mounting

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 9 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.17% for the current model date.

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

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 9 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

13 package states
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 9 affected package states 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 releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.52-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-intelAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative 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.

1 current
CVE-2023-53222 · CSAF 2.0 · revision 50 · interimSUSE Product Security TeamCVE-2023-53222
15 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
  • SLES 15 SP1 CHOST Images for Microsoft Azure
  • SLES 15 SP2 CHOST Images for Microsoft Azure
Summary
In the Linux kernel, the following vulnerability has been resolved: jfs: jfs_dmap: Validate db_l2nbperpage while mounting In jfs_dmap.c at line 381, BLKTODMAP is used to get a logical block number inside dbFree(). db_l2nbperpage, which is the log2 number of blocks per page, is passed as an argument to BLKTODMAP which uses it for shifting. Syzbot reported a shift out-of-bounds crash because db_l2nbperpage is too big. This happens because the large value is set without any validation in dbMount() at line 181. Thus, make sure that db_l2nbperpage is correct while mounting. Max number of blocks per page = Page size / Min block size => log2(Max num_block per page) = log2(Page size / Min block size) = log2(Page size) - log2(Min block size) => Max db_l2nbperpage = L2PSIZE - L2MINBLOCKSIZE
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2023-59862

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 9 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: jfs: jfs_dmap: Validate db_l2nbperpage while mounting In jfs_dmap.c at line 381, BLKTODMAP is used to get a logical block number inside dbFree(). db_l2nbperpage, which is the log2 number of blocks per page, is passed as an argument to BLKTODMAP which uses it for shifting. Syzbot reported a shift out-of-bounds crash because db_l2nbperpage is too big. This happens because the large value is set without any validation in dbMount() at line 181. Thus, make sure that db_l2nbperpage is correct while mounting. Max number of blocks per page = Page size / Min block size => log2(Max num_block per page) = log2(Page size / Min block size) = log2(Page size) - log2(Min block size) => Max db_l2nbperpage = L2PSIZE - L2MINBLOCKSIZE

What

In the Linux kernel, the following vulnerability has been resolved: jfs: jfs_dmap: Validate db_l2nbperpage while mounting In jfs_dmap.c at line 381, BLKTODMAP is used to get a logical block number inside dbFree(). db_l2nbperpage, which is the log2 number of blocks per page, is passed as an argument to BLKTODMAP which uses it for shifting. Syzbot reported a shift out-of-bounds crash because db_l2nbperpage is too big. This happens because the large value is set without any validation in dbMount() at line 181. Thus, make sure that db_l2nbperpage is correct while mounting. Max number of blocks per page = Page size / Min block size => log2(Max num_block per page) = log2(Page size / Min block size) = log2(Page size) - log2(Min block size) => Max db_l2nbperpage = L2PSIZE - L2MINBLOCKSIZE

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: jfs: jfs_dmap: Validate db_l2nbperpage while mounting In jfs_dmap.c at line 381, BLKTODMAP is used to get a logical block number inside dbFree(). db_l2nbperpage, which is the log2 number of blocks per page, is passed as an argument to BLKTODMAP which uses it for shifting. Syzbot reported a shift out-of-bounds crash because db_l2nbperpage is too big. This happens because the large value is set without any validation in dbMount() at line 181. Thus, make sure that db_l2nbperpage is correct while mounting. Max number of blocks per page = Page size / Min block size => log2(Max num_block per page) = log2(Page size / Min block size) = log2(Page size) - log2(Min block size) => Max db_l2nbperpage = L2PSIZE - L2MINBLOCKSIZE

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

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
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

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 → Out-of-bounds Read → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

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:L/UI:N/S:U/C:H/I:H/A:H

Common 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.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.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.
Denial of serviceCWE-125
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-2053Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250917SECURITY BULLETIN 17 SEPT 2025

The Cyber Security Agency of Singapore included this CVE in its official SECURITY BULLETIN 17 SEPT 2025, published on 17 September 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1032Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53206 Référence CVE CVE-2023-53207 https://www.cve.org/CVERecord?id=CVE-2023-53207 Référence CVE CVE-2023-53208 https://www.cve.org/CVERecord?id=CVE-2023-53208 Référence CVE CVE-2023-53209 https://www.cve.org/CVERecord?id=CVE-2023-53209 Référence CVE CVE-2023-53210 https://www.cve.org/CVERecord?id=CVE-2023-53210 Référence CVE CVE-2023-53215 https://www.cve.org/CVERecord?id=CVE-2023-53215 Référence CVE CVE-2023-53217 https://www.cve.org/CVERecord?id=CVE-2023-53217 Référence CVE CVE-2023-53220 https://www.cve.org/CVERecord?id=CVE-2023-53220 Référence CVE CVE-2023-53221 https://www.cve.org/CVERecord?id=CVE-2023-53221 Référence CVE CVE-2023-53222 https://www.cve.org/CVERecord?id=CVE-2023-53222 Référence CVE CVE-2023-53226 https://www.cve.org/CVERecord?id=CVE-2023-53226 Référence CVE CVE-2023-53230 https://www.cve.org/CVERecord?id=CVE-2023-53230 Référence CVE CVE-2023-53231 https://www.cve.org/CVERecord?id=CVE-2023-53231 Référence CVE CVE-2023-53235 https://www.cve.org/CVERecord?id=CVE-2023-53235 Référence CVE CVE-2023-53238 https://www.cve.org/CVERecord?id=CVE-2023-53238 Référence CVE CVE-2023-53243 https://www.cve.org/CVERecord?id=CVE-2023-53243 Référence CVE CVE-2023-53245 https://www.cve.org/CVERecord?id=CVE-2023-53245 Référence CVE CVE-2023-53247 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1009Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53206 Référence CVE CVE-2023-53207 https://www.cve.org/CVERecord?id=CVE-2023-53207 Référence CVE CVE-2023-53208 https://www.cve.org/CVERecord?id=CVE-2023-53208 Référence CVE CVE-2023-53209 https://www.cve.org/CVERecord?id=CVE-2023-53209 Référence CVE CVE-2023-53210 https://www.cve.org/CVERecord?id=CVE-2023-53210 Référence CVE CVE-2023-53215 https://www.cve.org/CVERecord?id=CVE-2023-53215 Référence CVE CVE-2023-53217 https://www.cve.org/CVERecord?id=CVE-2023-53217 Référence CVE CVE-2023-53220 https://www.cve.org/CVERecord?id=CVE-2023-53220 Référence CVE CVE-2023-53221 https://www.cve.org/CVERecord?id=CVE-2023-53221 Référence CVE CVE-2023-53222 https://www.cve.org/CVERecord?id=CVE-2023-53222 Référence CVE CVE-2023-53226 https://www.cve.org/CVERecord?id=CVE-2023-53226 Référence CVE CVE-2023-53230 https://www.cve.org/CVERecord?id=CVE-2023-53230 Référence CVE CVE-2023-53231 https://www.cve.org/CVERecord?id=CVE-2023-53231 Référence CVE CVE-2023-53235 https://www.cve.org/CVERecord?id=CVE-2023-53235 Référence CVE CVE-2023-53238 https://www.cve.org/CVERecord?id=CVE-2023-53238 Référence CVE CVE-2023-53243 https://www.cve.org/CVERecord?id=CVE-2023-53243 Référence CVE CVE-2023-53245 https://www.cve.org/CVERecord?id=CVE-2023-53245 Référence CVE CVE-2023-53247 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0921Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53209 Référence CVE CVE-2023-53210 https://www.cve.org/CVERecord?id=CVE-2023-53210 Référence CVE CVE-2023-53213 https://www.cve.org/CVERecord?id=CVE-2023-53213 Référence CVE CVE-2023-53215 https://www.cve.org/CVERecord?id=CVE-2023-53215 Référence CVE CVE-2023-53216 https://www.cve.org/CVERecord?id=CVE-2023-53216 Référence CVE CVE-2023-53217 https://www.cve.org/CVERecord?id=CVE-2023-53217 Référence CVE CVE-2023-53219 https://www.cve.org/CVERecord?id=CVE-2023-53219 Référence CVE CVE-2023-53220 https://www.cve.org/CVERecord?id=CVE-2023-53220 Référence CVE CVE-2023-53221 https://www.cve.org/CVERecord?id=CVE-2023-53221 Référence CVE CVE-2023-53222 https://www.cve.org/CVERecord?id=CVE-2023-53222 Référence CVE CVE-2023-53223 https://www.cve.org/CVERecord?id=CVE-2023-53223 Référence CVE CVE-2023-53226 https://www.cve.org/CVERecord?id=CVE-2023-53226 Référence CVE CVE-2023-53229 https://www.cve.org/CVERecord?id=CVE-2023-53229 Référence CVE CVE-2023-53230 https://www.cve.org/CVERecord?id=CVE-2023-53230 Référence CVE CVE-2023-53231 https://www.cve.org/CVERecord?id=CVE-2023-53231 Référence CVE CVE-2023-53234 https://www.cve.org/CVERecord?id=CVE-2023-53234 Référence CVE CVE-2023-53235 https://www.cve.org/CVERecord?id=CVE-2023-53235 Référence CVE CVE-2023-53238 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0895Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53209 Référence CVE CVE-2023-53210 https://www.cve.org/CVERecord?id=CVE-2023-53210 Référence CVE CVE-2023-53213 https://www.cve.org/CVERecord?id=CVE-2023-53213 Référence CVE CVE-2023-53215 https://www.cve.org/CVERecord?id=CVE-2023-53215 Référence CVE CVE-2023-53216 https://www.cve.org/CVERecord?id=CVE-2023-53216 Référence CVE CVE-2023-53217 https://www.cve.org/CVERecord?id=CVE-2023-53217 Référence CVE CVE-2023-53219 https://www.cve.org/CVERecord?id=CVE-2023-53219 Référence CVE CVE-2023-53220 https://www.cve.org/CVERecord?id=CVE-2023-53220 Référence CVE CVE-2023-53221 https://www.cve.org/CVERecord?id=CVE-2023-53221 Référence CVE CVE-2023-53222 https://www.cve.org/CVERecord?id=CVE-2023-53222 Référence CVE CVE-2023-53223 https://www.cve.org/CVERecord?id=CVE-2023-53223 Référence CVE CVE-2023-53226 https://www.cve.org/CVERecord?id=CVE-2023-53226 Référence CVE CVE-2023-53229 https://www.cve.org/CVERecord?id=CVE-2023-53229 Référence CVE CVE-2023-53230 https://www.cve.org/CVERecord?id=CVE-2023-53230 Référence CVE CVE-2023-53231 https://www.cve.org/CVERecord?id=CVE-2023-53231 Référence CVE CVE-2023-53232 https://www.cve.org/CVERecord?id=CVE-2023-53232 Référence CVE CVE-2023-53234 https://www.cve.org/CVERecord?id=CVE-2023-53234 Référence CVE CVE-2023-53235 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-030167Linux の Linux Kernel における境界外読み取りに関する脆弱性

Linux の Linux Kernel には、境界外読み取りに関する脆弱性が存在します。

Official advisory ↗
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
Fixed
Linux: < 2.6.12, 4.14.322 ≤ 4.14.*, 4.19.291 ≤ 4.19.*, 5.4.251 ≤ 5.4.*, 5.10.188 ≤ 5.10.*, 5.15.121 ≤ 5.15.*, 6.1.40 ≤ 6.1.*, 6.4.5 ≤ 6.4.*, 6.5 ≤ *
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 15 Sept 2025 · Last source change 5 Aug 2026, 09:13 UTC · CWE-125 · Out-of-bounds Read

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2023-59862
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2023-59862↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
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.
Free version - for non-commercial use only.CVE-2023-53222 · cve.blacktree.nl