Lucene search
+L

Scientific Linux Security Update : yum-conf on SL3.x i386/x86_64

🗓️ 01 Aug 2012 00:00:00Reported by TenableType 
nessus
 nessus
🔗 www.tenable.com👁 23 Views

Scientific Linux Security Update for SL3.x i386/x86_64 with essential yum-conf change

Refs
Code
SourceLink
nessuswww.nessus.org/u
#%NASL_MIN_LEVEL 70300
#
# (C) Tenable Network Security, Inc.
#
# The descriptive text is (C) Scientific Linux.
#

include('deprecated_nasl_level.inc');
include('compat.inc');

if (description)
{
  script_id(60331);
  script_version("1.6");
  script_set_attribute(attribute:"plugin_modification_date", value:"2021/01/14");

  script_name(english:"Scientific Linux Security Update : yum-conf on SL3.x i386/x86_64");
  script_summary(english:"Checks rpm output for the updated package");

  script_set_attribute(
    attribute:"synopsis", 
    value:"The remote Scientific Linux host is missing a security update."
  );
  script_set_attribute(
    attribute:"description", 
    value:
"yum-conf changes are needed for the transition of SL 3 into legacy
mode.

Changes from the old yum-conf

* The files /etc/yum.conf and /etc/cron.daily/yum.cron are not marked
as 'noreplace'. This means that if you have modified /etc/yum.conf or
/etc/cron.daily/yum.cron, your version will be saved as *.rpmsave and
the new version will be put in it's place.

* All the /etc/yum.conf.* files have been removed except yum.conf.309,
yum.conf.30x, and yum.conf.flash

* The yum.conf entries are pointing at /linux/scientific/obsolete/30*,
except for the errata area of /linux/scientific/309/ .

* The yum.cron (/etc/cron.daily/yum.cron) is the yum.cron from
yum-conf-309. It does not point to 309, but has the following changes.

  - The yum.cron uses your /etc/yum.conf. If your
    /etc/yum.conf has an excludes line already in it, it
    adds the entries in /etc/yum.d/yum.cron.excludes. If
    your /etc/yum.conf does not have an excludes line, it
    adds one, with the entries from /etc/yum.cron.excludes -
    It does not use /etc/yum.d/yum.cron.primary or
    /etc/yum.d/yum.cron.secondary. You need to put the list
    of yum repositories you want yum to go to in
    /etc/yum.conf

SL 3.0.1"
  );
  # https://listserv.fnal.gov/scripts/wa.exe?A2=ind0712&L=scientific-linux-errata&T=0&P=1888
  script_set_attribute(
    attribute:"see_also",
    value:"http://www.nessus.org/u?4f417bf9"
  );
  script_set_attribute(
    attribute:"solution", 
    value:"Update the affected yum-conf package."
  );
  script_set_attribute(attribute:"risk_factor", value:"High");

  script_set_attribute(attribute:"plugin_type", value:"local");
  script_set_attribute(attribute:"cpe", value:"x-cpe:/o:fermilab:scientific_linux");

  script_set_attribute(attribute:"patch_publication_date", value:"2007/12/13");
  script_set_attribute(attribute:"plugin_publication_date", value:"2012/08/01");
  script_set_attribute(attribute:"generated_plugin", value:"current");
  script_end_attributes();

  script_category(ACT_GATHER_INFO);
  script_copyright(english:"This script is Copyright (C) 2012-2021 and is owned by Tenable, Inc. or an Affiliate thereof.");
  script_family(english:"Scientific Linux Local Security Checks");

  script_dependencies("ssh_get_info.nasl");
  script_require_keys("Host/local_checks_enabled", "Host/cpu", "Host/RedHat/release", "Host/RedHat/rpm-list");

  exit(0);
}


include("audit.inc");
include("global_settings.inc");
include("rpm.inc");


if (!get_kb_item("Host/local_checks_enabled")) audit(AUDIT_LOCAL_CHECKS_NOT_ENABLED);
release = get_kb_item("Host/RedHat/release");
if (isnull(release) || "Scientific Linux " >!< release) audit(AUDIT_HOST_NOT, "running Scientific Linux");
if (!get_kb_item("Host/RedHat/rpm-list")) audit(AUDIT_PACKAGE_LIST_MISSING);

cpu = get_kb_item("Host/cpu");
if (isnull(cpu)) audit(AUDIT_UNKNOWN_ARCH);
if (cpu >!< "x86_64" && cpu !~ "^i[3-6]86$") audit(AUDIT_LOCAL_CHECKS_NOT_IMPLEMENTED, "Scientific Linux", cpu);


flag = 0;
if (rpm_check(release:"SL3", cpu:"i386", reference:"yum-conf-301-8.SL")) flag++;


if (flag)
{
  if (report_verbosity > 0) security_hole(port:0, extra:rpm_report_get());
  else security_hole(0);
  exit(0);
}
else audit(AUDIT_HOST_NOT, "affected");

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation