← Back to results
Vulnerability record · public intelligence
CVE-2024-39771
MEDIUM

CVE-2024-39771

Published Aug 28, 2024 · Updated Oct 23, 2026

Severity · CVSSMEDIUM · 6.8
Known exploitationNot listed
EPSS / likelihood0.12%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

QBiC CLOUD CC-2L v1.1.30 and earlier and Safie One v1.8.2 and earlier do not properly validate certificates, which may allow a network-adjacent unauthenticated attacker to obtain and/or alter communications of the affected product via a man-in-the-middle attack.

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

QBiC CLOUD CC-2L v1.1.30 and earlier and Safie One v1.8.2 and earlier do not properly validate certificates, which may allow a network-adjacent unauthenticated attacker to obtain and/or alter communications of the affected product via a man-in-the-middle attack.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. safie.jp ↗
  2. jvn.jp ↗

Record history

Published Aug 28, 2024 · Last refreshed Oct 23, 2026