惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

爱范儿
爱范儿
T
The Blog of Author Tim Ferriss
G
Google Developers Blog
博客园_首页
博客园 - 【当耐特】
量子位
S
SegmentFault 最新的问题
B
Blog RSS Feed
酷 壳 – CoolShell
酷 壳 – CoolShell
V
Visual Studio Blog
T
Tailwind CSS Blog
阮一峰的网络日志
阮一峰的网络日志
V
V2EX
Y
Y Combinator Blog
博客园 - 聂微东
The Cloudflare Blog
小众软件
小众软件
J
Java Code Geeks
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
月光博客
月光博客
H
Help Net Security
Jina AI
Jina AI
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
宝玉的分享
宝玉的分享

Okta Trust

Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe Forum21 Europe
Forum21 Europe
Okta, Inc. · 2026-09-08 · via Okta Trust

Description

The Okta Hyperdrive Integration installer does not mask the OAuth client secret when passed as an MSI property. The credential is recorded in plaintext in the installer log, the Application Event Log, and the process command line, all of which are readable by an authenticated local user on the workstation.

Affected product and versions

Customers using the Okta Hyperdrive Integration plugin versions 1.2.0 through 1.5.1 are affected.

Preconditions

This applies if the following preconditions are present:

  • The agent was installed with the OAuth client secret passed as an MSI property on the installer command line,

  • A user has local authenticated access on the Windows host where the agent was installed.

Customer Recommendations

To remediate this vulnerability, upgrade the Okta Hyperdrive Integration plugin to version 1.5.2 or greater.

Download version 1.5.2 of the Okta Hyperdrive Integration plugin

Resolution

The vulnerability is present in the Okta Hyperdrive Integration plugin versions 1.2.0 to 1.5.1 and has been resolved in version 1.5.2.

CVE details