nday
CVE-2007-6629

Interpretation conflict in LScube Feng 0.1.15 and earlier allows remote attackers to cause a…Title composed by nday; the CVE record has none.

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

network
AV:N in AV:N/AC:L/Au:N/C:N/I:N/A:P (CVSS 2.0) from NVD's analysts
no authentication required
Au:N in AV:N/AC:L/Au:N/C:N/I:N/A:P (CVSS 2.0) from NVD's analysts

CVSS 2.0 has no user-interaction metric, so “no user interaction” and “remote, unauthenticated” are never assigned from a CVSS 2.0 vector.

stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2008-01-04T00:00Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

Interpretation conflict in LScube Feng 0.1.15 and earlier allows remote attackers to cause a denial of service (NULL dereference and daemon crash) via a User-Agent header line that contains a carriage-return character, which is considered a line delimiter when the header is split into individual lines, but not when log_user_agent in RTSP_utils.c parses the content of the User-Agent line.

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by mitre.

src cvelist · nday , bulk import · raw
{
  "id": 102002,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2007-6629",
  "occurred_at": "2008-01-04T00:00:00Z",
  "observed_at": "2026-11-13T05:35:52.818273Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2008-01-04T00:00:00.000Z",
    "assigner_short_name": "mitre"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.