LiveActive security incident?Get immediate response
CVE Record

CVE-2014-5470: Actual Analyzer through 2014-08-29 allows code execution via shell metacharacters because untrusted input i...

Actual Analyzer through 2014-08-29 allows code execution via shell metacharacters because untrusted input is used for part of the input data passed to an eval operation.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Actual Analyzer versions through 2014-08-29 can allow remote code execution when attacker-controlled input reaches an eval operation with shell metacharacters. The business risk is full compromise of affected exposed systems. The source bundle does not identify a vendor patch or supported product metadata.

Executive priority

Treat as urgent if the product is present or externally reachable. The potential impact is system takeover, but confidence depends on confirming whether this legacy software exists in the environment.

Technical view

CVE-2014-5470 is a critical CWE-77 command-injection style flaw. CVSS 3.1 is 9.8: network reachable, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to environments still running Actual Analyzer through 2014-08-29, especially internet-accessible instances. The bundle lacks CPEs, vendor details, and deployment context, so asset confirmation requires local inventory checks.

Exploitation context

Exploit-DB and Vulmon references are listed, indicating public exploit information exists. The CVE is not marked CISA KEV in the bundle, and no cited source here confirms active exploitation.

Researcher notes

The CVE record gives strong severity and root-cause signals but sparse product metadata. Avoid assuming patch status. Use the exploit references only to understand affected behavior and detection needs, not to validate offensively.

Mitigation direction

  • Identify and prioritize any Actual Analyzer deployments.
  • Check vendor or project guidance for fixed versions or retirement advice.
  • Remove internet exposure until remediation is confirmed.
  • Apply compensating controls around affected interfaces.
  • Retire unsupported instances if no maintained fix exists.

Validation and detection

  • Confirm whether Actual Analyzer exists in asset inventory.
  • Verify version or build date against 2014-08-29.
  • Check whether the service is reachable from untrusted networks.
  • Review logs for suspicious input-handling errors or unexpected process activity.
  • Document whether vendor remediation guidance is available.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-77: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter 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 lookup
description · low confidence lookup

Execution 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 lookup
cve · low confidence lookup

CVE-2014-5470 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

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

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2014-5470Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-77 · source CWE mapping

Improper Neutralization of Special Elements used in a Command ('Command Injection')

Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.