dbcve.org
LatdApplication · Debian

CVE-2013-0251

HIGH · 10.0 CVSS v2.0 Published 2013-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Stack-based buffer overflow in llogincircuit.cc in latd 1.25 through 1.30 and earlier allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long string in the llogin version.

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 confidence

Stack-based buffer overflow in llogincircuit.cc within the latd daemon (versions 1.25-1.30 and earlier). The vulnerability is triggered by sending a long string in the llogin version field, allowing remote attackers to potentially execute arbitrary code or crash the service.

MitigationUpgrade latd to a patched version beyond 1.30, or implement input validation/bounds checking on the llogin version string in llogincircuit.cc to prevent buffer overflow.

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
LatdApplication
Affected:= 1.25= 1.26= 1.27= 1.28= 1.29= 1.30

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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if latd package is installed
    On Debian systems, run: dpkg -l | grep latd or dpkg -s latd
    Affected if latd package is installed with version 1.25, 1.26, 1.27, 1.28, 1.29, or 1.30 (or earlier)
  2. Verify latd daemon version
    Run: latd -v or check /usr/sbin/latd --version if available, or dpkg -s latd to see the installed version
    Affected if The reported version is 1.30 or lower
  3. Check if latd service is running
    Run: ps aux | grep latd or systemctl status latd
    Affected if latd daemon is actively running and accepting connections
  4. Verify network exposure
    Check if port 513/tcp (LAT protocol) is listening: netstat -tlnp | grep 513 or ss -tlnp | grep 513
    Affected if latd is listening on network ports, making the vulnerability remotely exploitable

User is affected if latd version 1.30 or earlier is installed AND the daemon is running and network-accessible, allowing external connection to the llogin version field.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade latd to a patched version beyond 1.30, or implement input validation/bounds checking on the llogin version string in llogincircuit.cc to prevent buffer overflow.

Fix this in Latd Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0251 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0251 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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