Authenticated privilege escalation via undisclosed access-control flaw
Published Nov 13, 2024 · Updated Nov 14, 2024
Improper access control in Intel BigDL before 2.5.0 allows remote authenticated users to elevate privileges via adjacent access. Intel identifies neither the affected component nor the incorrect access-control operation, and no public patch detail discloses the mechanism. Exploitation requires an authenticated low-privileged account and adjacent reachability; the scope of the elevated authority is unspecified.
Summary
What happened
Improper access control in Intel BigDL before 2.5.0 allows remote authenticated users to elevate privileges via adjacent access. Intel identifies neither the affected component nor the incorrect access-control operation, and no public patch detail discloses the mechanism. Exploitation requires an authenticated low-privileged account and adjacent reachability; the scope of the elevated authority is unspecified.
The record
- CVE
- CVE-2024-29085
- Published
- Nov 13, 2024
- Updated
- Nov 14, 2024
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- BigDL
- Classifications
- CWE-284, T1068
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 13, 2024CVE publishedPublication date reported by the CVE source.
- Nov 14, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=before version 2.5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo