Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-38970: vaeThink 1.0.2 is vulnerable to Information Disclosure via the system backend,access management administrator

27
Routine
MEDIUM 4.9DOWNGRADE

CVE-2024-38970 is a medium-severity flaw (CVSS 4.9) affecting vaethink. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

vaeThink 1.0.2 is vulnerable to Information Disclosure via the system backend,access management administrator function.

Why this priority

  • No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score4.9 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededHigh
User interactionNone
EPSS exploit chance0.4% (top 62%)
CISA exploited listNo
WeaknessCWE-200
Published2024-07-09
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: vaethink

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

vaethink vaethink DOWNGRADE
Affected: 1.0.2
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.0.2
1. Check installed version
apt-cache policy vaethink || rpm -q vaethink || vaethink --version
2. No fixed release: DOWNGRADE to a release before 1.0.2 (Debian / Ubuntu)
apt-cache madison vaethink sudo apt install vaethink=<VERSION_BEFORE_1.0.2> sudo apt-mark hold vaethink
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list vaethink sudo dnf downgrade vaethink-<VERSION_BEFORE_1.0.2> sudo dnf versionlock add vaethink
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-38970?

vaethink: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-38970 being exploited?

CVE-2024-38970 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-38970 affect?

CVE-2024-38970 affects vaethink. Severity is medium (CVSS 4.9). vaeThink 1.0.2 is vulnerable to Information Disclosure via the system backend,access management administrator function.

How urgent is CVE-2024-38970?

Priority 27/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.