CVE-2013-1771
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 web server Monkeyd produces a world-readable log (/var/log/monkeyd/master.log) on gentoo.
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 web server 'Monkeyd' creates a log file at /var/log/monkeyd/master.log on Gentoo with world-readable permissions (mode 644), allowing any local or remote user to read potentially sensitive HTTP request/response data, authentication credentials, and server operational details exposed in logs.
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 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/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 Monkey daemon is installedCheck for the presence of the monkeyd binary or package using: which monkeyd or ls /usr/sbin/monkeyd or package manager query (e.g., equo q list monkeyd on Gentoo)Affected if monkeyd binary or package is found on the system
-
Locate the Monkey log fileVerify the log file exists at /var/log/monkeyd/master.log using: ls -la /var/log/monkeyd/master.logAffected if The file /var/log/monkeyd/master.log exists on the system
-
Check log file permissionsRun: stat -c '%a' /var/log/monkeyd/master.log or ls -la /var/log/monkeyd/master.log to view the octal mode (e.g., 644)Affected if The file permissions grant read access to 'others' (mode ends with 4 or 5, such as 644, 654, or 644 with group read) - the last digit being 4 or higher indicates world-readable
-
Verify parent directory permissionsCheck the permissions on the parent directory: stat -c '%a' /var/log/monkeyd or ls -ld /var/log/monkeydAffected if The directory permissions allow access to non-privileged users (world-executable or more permissive, such as 755)
If monkeyd is installed and the master.log file exists with permissions that allow any user (others) to read it (mode 644 or similar), the environment is vulnerable to unauthorized information disclosure.
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 dataChange log file permissions to 640 or more restrictive (owner/group readable only) and ensure the parent directory /var/log/monkeyd has appropriate access controls to prevent unauthorized access.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1771 — 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-2013-1771 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