CVE-2014-3930
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 · uneditedlg.pl in Cistron-LG 1.01 stores sensitive information under the web root with insufficient access controls, which allows remote attackers to obtain IP addresses and other unspecified router credentials.
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 lg.pl script in Cistron-LG 1.01 stores sensitive information including IP addresses and router credentials under the web root without proper access controls, allowing remote attackers to directly download or access this sensitive data via HTTP requests.
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= 1.01CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/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 Lg Project Lg versionLocate and inspect the lg.pl script in your web server's cgi-bin or script directory. Check the script header or any version identifier within the file for version number 1.01.Affected if The installed version is Lg Project Lg 1.01
-
Identify sensitive data storage locationsSearch the web server document root and cgi directories for configuration or data files that may contain IP addresses, router credentials, or authentication tokens. Look for files with names suggesting sensitive content (e.g., config, passwords, credentials, data, devices).Affected if Files containing IP addresses, credentials, or sensitive configuration data exist under the web root directory
-
Test HTTP access to sensitive filesUsing a web browser or curl command, attempt to directly request any identified sensitive files via HTTP (e.g., http://yourserver/cgi-bin/lg/devices.conf or similar paths where sensitive data files may be stored).Affected if Sensitive files are directly accessible and downloadable via HTTP requests without authentication
-
Review file permissions on data directoriesCheck the file system permissions on directories under the web root that contain the lg.pl script and any associated data files. Verify if read permissions allow world-readable access.Affected if Sensitive data files have permissions allowing unauthenticated web-based read access
-
Inspect lg.pl for hardcoded credentialsExamine the lg.pl script source code for hardcoded IP addresses, passwords, or authentication strings that may be logged or stored by the application.Affected if The script contains or stores credentials in plaintext files accessible via the web server
If Lg Project Lg 1.01 is installed and sensitive files containing credentials or IP addresses are directly accessible via HTTP under the web root, the environment is affected by this vulnerability.
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 dataRelocate sensitive data storage outside the web root directory or implement proper file system permissions to prevent unauthorized web-based access to stored credentials and configuration data.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3930 — 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-2014-3930 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