LDAP Bind Password Exposure in AxxonNet ARP Agent Logs
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.25.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.25.0.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 6/100 · provisional
- Fix
- Fixed in 3.25.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The ARP Agent component of AxxonSoft AxxonNet (versions prior to 3.25.0) on Windows and Linux can write the plaintext password of its LDAP directory service account into its log files. A local user who can read those logs or the generated support packages could recover that password.
Read the original description
Insertion of Sensitive Information into Log File (CWE-532) in the ARP Agent component in AxxonSoft AxxonNet before 3.25.0 on Windows and Linux allows a local attacker with read access to ARP Agent log files or support packages to obtain the plaintext password of the LDAP directory service account via WARNING-level log entries that contain serialized user synchronization data.
What to do
Upgrade to a fixed version: 3.25.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- AxxonSoft AxxonNet ARP Agent
fixed in 3.25.0
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.