Security readout for executives and security teams
Plain-English summary
CVE-2024-51367 is a critical file-upload flaw reported in BlackBoard v2.0.0.2. An unauthenticated attacker could upload a crafted XML file and gain arbitrary code execution. The public record is sparse, so exposure depends on whether this specific BlackBoard component is deployed and reachable.
Executive priority
Treat as urgent for any confirmed deployment because the reported impact is full compromise without authentication or user interaction. Prioritize discovery first, because product metadata is incomplete and patch guidance is not present in the supplied sources.
Technical view
The CVE describes arbitrary file upload in the \Users\username.BlackBoard component of BlackBoard v2.0.0.2, mapped to CWE-94. CVSS 3.1 is 9.8 with network access, low complexity, no privileges, and no user interaction. The source bundle names a public GitHub PoC reference but no vendor patch details.
Likely exposure
Highest concern is internet- or intranet-reachable BlackBoard v2.0.0.2 instances exposing the named upload component. The CVE metadata lists vendor and product as n/a, so asset identification may require local software inventory rather than CPE matching.
Exploitation context
The source bundle includes a public GitHub PoC reference, indicating public technical detail exists. The CVE is not listed as KEV in the supplied data, and the sources do not establish active exploitation in the wild.
Researcher notes
Key gaps are vendor identity, affected CPEs, patch status, and real-world exploitation evidence. Avoid assuming Blackboard Learn or other similarly named products are affected; the source bundle only supports BlackBoard v2.0.0.2 and the named component.
Mitigation direction
- Identify any BlackBoard v2.0.0.2 deployments and owners.
- Check vendor or maintainer guidance for patches or configuration changes.
- Restrict network access to the affected component where possible.
- Disable or isolate the upload functionality if business operations allow.
- Monitor for unexpected XML uploads or process execution from upload paths.
Validation and detection
- Confirm whether BlackBoard v2.0.0.2 exists in asset inventory.
- Verify whether the \Users\username.BlackBoard component is deployed and reachable.
- Review web and application logs for suspicious XML upload activity.
- Check file-system locations tied to uploads for unexpected executable artifacts.
- Document compensating controls if no vendor fix is available.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-51367 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Gelcon/PoCofBlackBoard2.0.0.2CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.