CVE-2024-39290
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsufficiently protected credentials issue exists in AIPHONE IX SYSTEM and IXG SYSTEM. A network-adjacent unauthenticated attacker may obtain sensitive information such as a username and its password in the address book.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInsufficiently protected credentials in AIPHONE IX SYSTEM and IXG SYSTEM allow a network-adjacent unauthenticated attacker to obtain usernames and passwords stored in the address book, likely due to weak encryption or cleartext storage of sensitive credential data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm the product modelIdentify the exact AIPHONE system model in your environment (IX SYSTEM or IXG SYSTEM) by checking the device label, management interface, or documentationAffected if The model is AIPHONE IX SYSTEM or IXG SYSTEM
-
Verify address book configurationAccess the system management interface and check if the address book feature is enabled and contains stored contact entries with credentialsAffected if Address book is populated with usernames and passwords for system access or door stations
-
Inspect credential storage methodExamine the system configuration files, backup files, or management interface for how credentials are stored in the address book - look for cleartext passwords or weak encryption indicatorsAffected if Credentials appear in plain text or use reversible encoding in configuration/backup files
-
Check network exposureDetermine if the system management interface is accessible to network-adjacent attackers (same VLAN or connected network segment without proper network segmentation)Affected if The system is accessible to unauthenticated network-adjacent attackers without additional access controls
-
Review firmware versionCheck the installed firmware version through the management interface or system status page if availableAffected if The firmware version predates any security updates addressing credential protection
The environment is affected if it runs AIPHONE IX SYSTEM or IXG SYSTEM with address book entries containing stored credentials accessible to network-adjacent attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataContact AIPHONE for firmware/security updates that implement proper credential protection (encryption/hashing). If no update is available, restrict network access to these systems and monitor for unauthorized access attempts.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39290 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-39290 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data