|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PROPOSAL] Cluster RECENT-76 - 40 candidates
- To: "Steven M. Christey" <coley@linus.mitre.org>
- Subject: Re: [PROPOSAL] Cluster RECENT-76 - 40 candidates
- From: Troy Bollinger <troy@austin.ibm.com>
- Date: Mon, 4 Feb 2002 22:10:03 -0600
- Cc: cve-editorial-board-list@lists.mitre.org
- Delivery-Date: Mon Feb 4 23:10:09 2002
- In-Reply-To: <200202010001.TAA04876@linus.mitre.org>; from coley@LINUS.MITRE.ORG on Thu, Jan 31, 2002 at 07:01:43PM -0500
- References: <200202010001.TAA04876@linus.mitre.org>
- User-Agent: Mutt/1.2.5si
Quoting Steven M. Christey (coley@LINUS.MITRE.ORG):
> ======================================================
> Candidate: CAN-2001-1061
> URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2001-1061
> Final-Decision:
> Interim-Decision:
> Modified:
> Proposed: 20020131
> Assigned: 20020131
> Category: SF
> Reference: AIXAPAR:IY22255
> Reference: URL:http://archives.neohapsis.com/archives/aix/2001-q3/0003.html
>
> Vulnerability in lsmcode in unknown versions of AIX, possibly related
> to a usage error.
>
> Analysis
> ----------------
> ED_PRI CAN-2001-1061 3
> Vendor Acknowledgement: yes
> Content Decisions: VAGUE
>
> CD:VAGUE states that if a vendor releases a vague report of a security
> problem, that even though there is insufficient detail, the problem
> should be included in CVE.
>
> Voting Section
> --------------
> Possible votes: ACCEPT/MODIFY/NOOP/REVIEWING/RECAST/REJECT
> If ACCEPT or MODIFY, include reason for acceptance:
> VERIFIED-BY-MY-ORG, ACKNOWLEDGED-BY-VENDOR, VERIFIED-BY-SOMEONE-I-TRUST,
> HAS-INDEPENDENT-CONFIRMATION, or provide other reason.
>
> VOTE: MODIFY
> ACCEPT_REASON: VERIFIED-BY-MY-ORG
>
> COMMENTS: Affects AIX 4.3 with bos.diag.util versions less than
> 4.3.3.75 and AIX 5.1 with bos.diag.util versions less than 5.1.0.10.
> The 4.3 APAR is IY22255 and the 5.1 APAR is IY22266.
>
>
--
Troy Bollinger <troy@austin.ibm.com>
Network Security Analyst
PGP keyid: 1024/0xB7783129
Troy's opinions are not IBM policy
|
|
