NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
107 matching advisories · page 2 of 4Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2021-3469 Foreman versions before 2.3.4 and before 2.4.0 is affected by an improper authorization handling flaw. theforeman · foreman 2021-06-03 medium6.5 CVE-2020-10716 A flaw was found in Red Hat Satellite's Job Invocation, where the "User Input" entry was not properly restricted to the view. redhat · satellite, redhat · satellite_capsule, theforeman · foreman_ansible 2021-05-27 medium6.1 CVE-2021-3457 An improper authorization handling flaw was found in Foreman. theforeman · smart_proxy_shell_hooks 2021-05-12 medium5.9 CVE-2021-3494 A smart proxy that provides a restful API to various sub-systems of the Foreman is affected by the flaw which can cause a Man-in-the-Middle attack. theforeman · foreman 2021-04-26 medium6.3 CVE-2021-3413 A flaw was found in Red Hat Satellite in tfm-rubygem-foreman_azure_rm in versions before 2.2.0. theforeman · foreman_azurerm, redhat · satellite 2021-04-08 medium5.5 CVE-2014-0241 rubygem-hammer_cli_foreman: File /etc/hammer/cli.modules.d/foreman.yml world readable theforeman · hammer_cli, redhat · satellite 2019-12-13 medium5.3 CVE-2014-0091 Foreman has improper input validation which could lead to partial Denial of Service theforeman · foreman 2019-12-11 high7.5 CVE-2013-4120 Katello has a Denial of Service vulnerability in API OAuth authentication theforeman · katello 2019-12-10 medium5.4 CVE-2013-0283 Katello: Username in Notification page has cross site scripting theforeman · katello 2019-12-05 medium5.4 CVE-2013-2101 Katello has multiple XSS issues in various entities theforeman · katello, redhat · satellite 2019-12-03 low2.7 CVE-2019-14825 Katello cleartext password storage issue rubygems · katello 2019-11-25 high7.4 CVE-2014-8183 It was found that foreman, versions 1.x.x before 1.15.6, in Satellite 6 did not properly enforce access controls on certain resources. theforeman · foreman, redhat · satellite 2019-08-01 medium6.5 CVE-2019-10198 An authentication bypass vulnerability was discovered in foreman-tasks before 0.15.7. theforeman · foreman-tasks, redhat · satellite 2019-07-31 medium4.9 CVE-2019-3893 In Foreman it was discovered that the delete compute resource operation, when executed from the Foreman API, leads to the disclosure of the plaintext password … theforeman · foreman, redhat · satellite 2019-04-09 medium5.4 CVE-2018-16887 katello Cross-site Scripting vulnerability rubygems · katello 2019-01-13 medium4.3 CVE-2018-14623 katello SQL Injection vulnerability rubygems · katello 2018-12-14 high7.6 CVE-2018-16861 A cross-site scripting (XSS) flaw was found in the foreman component of satellite. theforeman · foreman 2018-12-07 medium5.4 CVE-2018-14664 A flaw was found in foreman from versions 1.18. theforeman · foreman 2018-10-12 critical9.8 CVE-2018-14643 smart_proxy_dynflow gem authentication bypass in Foreman remote execution feature rubygems · smart_proxy_dynflow 2018-09-21 medium4.3 CVE-2016-7078 foreman before version 1.15.0 is vulnerable to an information leak through organizations and locations feature. theforeman · foreman 2018-09-10 medium4.3 CVE-2016-7077 foreman before 1.14.0 is vulnerable to an information leak. theforeman · foreman 2018-09-10 medium4.3 CVE-2017-2662 katello Improper Privilege Management vulnerability rubygems · katello 2018-08-22 medium6.1 CVE-2016-8639 It was found that foreman before 1.13.0 is vulnerable to a stored XSS via an organization or location name. theforeman · foreman, redhat · satellite, redhat · satellite_capsule 2018-08-01 medium6.1 CVE-2016-8634 A vulnerability was found in foreman 1.14.0. theforeman · foreman 2018-08-01 medium6.4 CVE-2016-8613 A flaw was found in foreman 1.5.1. theforeman · foreman 2018-07-31 high7.3 CVE-2016-9595 A flaw was found in katello-debug before 3.4.0 where certain scripts and log files used insecure temporary files. theforeman · katello, redhat · satellite, redhat · satellite_capsule 2018-07-27 medium6.1 CVE-2017-7535 foreman before version 1.16.0 is vulnerable to a stored XSS in organizations/locations assignment to hosts. theforeman · foreman 2018-07-26 medium6.5 CVE-2017-2672 A flaw was found in foreman before version 1.15 in the logging of adding and registering images. theforeman · foreman, redhat · satellite 2018-06-21 medium4.7 CVE-2016-9593 foreman-debug before version 1.15.0 is vulnerable to a flaw in foreman-debug's logging. theforeman · foreman, redhat · satellite 2018-04-16 medium6.5 CVE-2018-1096 An input sanitization flaw was found in the id field in the dashboard controller of Foreman before 1.16.1. theforeman · foreman, redhat · satellite 2018-04-05

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.