CVE-2024-1367
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 · uneditedA command injection vulnerability exists where an authenticated, remote attacker with administrator privileges on the Security Center application could modify Logging parameters, which could lead to the execution of arbitrary code on the Security Center host.
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 confidenceA command injection vulnerability exists in Tenable Security Center's Logging parameters configuration. An authenticated attacker with administrator privileges can inject arbitrary OS commands through the logging configuration settings, leading to remote code execution on the Security Center host.
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< 6.3.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm Tenable Security Center is installedIdentify if Tenable Security Center is present in your environment by checking for the application process or installation directory. Common locations include /opt/sc or checking for the 'sc' service process.Affected if Tenable Security Center is not installed in the environment, the system is not affected.
-
Determine the installed versionCheck the installed version of Tenable Security Center using the application's web interface (typically under Help > About or System > Diagnostics) or by querying the application directly. Compare your version against the affected range of < 6.3.0.Affected if The installed version is 6.3.0 or higher, the system is not vulnerable to this specific CVE.
-
Verify administrator account existenceReview the list of administrator-level accounts in Tenable Security Center by accessing the Users or Accounts management section within the Security Center interface.Affected if No administrator accounts exist, exploitation is not possible through this attack vector, though the vulnerability still exists in the code path.
-
Inspect logging configuration parametersAccess the Logging configuration settings within Tenable Security Center (typically under Settings > Logging or System Configuration > Logging). Examine any fields that accept parameters for logging operations such as syslog destinations, log rotation paths, or custom logging commands.Affected if Logging configuration accepts user-supplied input without sanitization and the system runs an affected version, the command injection vulnerability is present.
The environment is affected if Tenable Security Center version is less than 6.3.0 and administrator accounts exist, as the command injection flaw exists in the logging parameter configuration path.
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 · scoped6.3.0
Restrict administrator access to trusted personnel only, apply vendor patches when available, and implement input validation/sanitization on all logging parameter fields to prevent command injection.
6.3.0 or later
- Upgrade Tenable Security Center to version 6.3.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1367 — 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-1367 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