CiscosecureApplication · Cisco
CVE-1999-0734
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 · uneditedA default configuration of CiscoSecure Access Control Server (ACS) allows remote users to modify the server database without authentication.
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 confidenceCiscoSecure Access Control Server (ACS) ships with a default configuration that permits remote users to modify the server database without any authentication, enabling an attacker to manipulate user accounts, access policies, or other critical ACS data remotely.
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 data
CiscosecureApplication
all versionsCVSS 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.
-
Identify if CiscoSecure ACS is installedCheck for CiscoSecure ACS installation by examining common installation directories (typically C:\Program Files\CiscoSecure ACS or C:\CiscoSecureACS) or check Windows Services for 'CiscoSecure ACS' serviceAffected if The CiscoSecure ACS software is found running on the system
-
Verify remote administration accessibilityAttempt to access the ACS web interface remotely on common ports (2002 for prior versions, or check the configured admin port) or examine httpd.conf or CSAdmin.ini for remote listener bindingsAffected if The ACS admin interface is accessible from network addresses other than localhost/127.0.0.1
-
Check remote database modification configurationExamine the ACS configuration files (CSAdmin.ini, CSLog.conf, or equivalent config files in the ACS directory) for settings controlling remote database updates - look for parameters like 'RemoteWriteAccess', 'AllowRemoteConfig', or similar authentication-required settingsAffected if Remote database modification is permitted without authentication (default vulnerable state)
-
Confirm authentication requirement for remote changesReview ACS admin settings within the web interface or configuration files to verify whether remote administration requires valid credentials - check for 'Require Authentication' or 'Local Admin Only' type settingsAffected if Remote modifications to user accounts or policies can be performed without providing admin credentials
A user is affected if CiscoSecure ACS is running and its default configuration allows remote, unauthenticated modifications to the server database or administrative settings.
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 dataModify the default configuration to require authentication for all remote database modifications. Disable or restrict remote administrative access and implement proper access controls.
Fix this in Ciscosecure
Scoped from the published advisory
- 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-0734 — 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-0734 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