LiveActive security incident?Get immediate response
CVE Record

CVE-2022-23347: BigAnt Software BigAnt Server v5.6.06 was discovered to be vulnerable to directory traversal attacks.

BigAnt Software BigAnt Server v5.6.06 was discovered to be vulnerable to directory traversal attacks.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-23347 reports a directory traversal vulnerability in BigAnt Software BigAnt Server v5.6.06. In business terms, this class of issue can allow access to files outside intended directories. The public record is sparse: no CVSS score, patch version, or confirmed exploitation is provided in the supplied sources.

Executive priority

Treat this as a targeted follow-up item, not a confirmed emergency from the supplied evidence. Inventory first, reduce exposure, and seek vendor-confirmed remediation for any BigAnt Server v5.6.06 deployment.

Technical view

The CVE description states BigAnt Server v5.6.06 is vulnerable to directory traversal. The source bundle references a public proof-of-concept repository and the vendor site, but does not define affected CPEs, vulnerable endpoints, prerequisites, impact scope, or fixed versions.

Likely exposure

Exposure is likely limited to organizations running BigAnt Server v5.6.06. Risk increases if the affected service is reachable from untrusted networks. The supplied sources do not identify other affected versions or deployment conditions.

Exploitation context

A public proof-of-concept reference exists in the CVE sources. CISA KEV status is false, and the supplied bundle provides no evidence of active exploitation in the wild.

Researcher notes

The public CVE data is minimal. It identifies the product/version and vulnerability class, with a PoC reference, but lacks CVSS, CWE, affected CPEs, vulnerable component details, prerequisites, and fix information.

Mitigation direction

  • Inventory BigAnt Server deployments and confirm exact versions.
  • Prioritize v5.6.06 systems for vendor review and compensating controls.
  • Check BigAnt vendor guidance for fixed versions or supported mitigation.
  • Restrict service access to trusted networks where operationally possible.
  • Monitor relevant logs for suspicious file access patterns.

Validation and detection

  • Confirm whether any deployed instance reports version 5.6.06.
  • Review external and internal exposure of BigAnt Server services.
  • Check vendor advisories or release notes for remediation guidance.
  • Assess logs for unusual path traversal or unexpected file retrieval indicators.
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.

description · low confidence lookup

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

CVE-2022-23347 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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