CVE-1999-0707
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 · uneditedThe default FTP configuration in HP Visualize Conference allows conference users to send a file to other participants without authorization.
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 confidenceThe default FTP configuration in HP Visualize Conference lacks proper authorization controls, allowing any conference participant to send files directly to other participants without requiring authentication or permission from the recipient.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versions= 10.20CVSS 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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Determine if HP Visualize Conference FTP is installedCheck the system for installed packages or services related to HP Visualize Conference FTP. On HP-UX systems, use 'swlist' or check for known installation directories. Look for process names associated with the conference FTP service.Affected if HP Visualize Conference FTP software is present on the system
-
Identify if the FTP service is runningCheck for active network listeners on FTP ports (typically port 21). Use commands like 'netstat -an' or 'lsof -i :21' to identify if an FTP service is actively listening. Also check running processes for conference-related FTP daemons.Affected if The FTP service associated with HP Visualize Conference is actively running and accepting connections
-
Inspect FTP server configuration for authorization controlsLocate and examine the configuration files for the HP Visualize Conference FTP server. Look for settings that control file transfer authorization, permission requirements, or access control lists. Check whether the service requires recipient confirmation before file transfers.Affected if The FTP configuration lacks or disables authorization checks, allowing unauthenticated or unapproved file transfers between participants
-
Verify network exposure of the FTP serviceDetermine if the FTP service is accessible from network segments where untrusted conference participants may connect. Check firewall rules, TCP wrappers, or service binding addresses that control who can reach the FTP service.Affected if The FTP service is exposed to network segments containing untrusted or unauthorized conference participants
A system is affected if HP Visualize Conference FTP is installed with its default configuration, the service is running, and authorization controls for peer-to-peer file transfers are not enforced.
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 dataRestrict or reconfigure the FTP service to enforce authorization checks before file transfers; disable the FTP service if unnecessary or implement proper access control mechanisms.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0707 — 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-1999-0707 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