Fixed bug caused by a host with missing attributes.

[Script-Nomad]

In certain cases, Nessus scans which contain hosts with no information other than Nessus Configuration settings. These settings appear as "Info" vulnerability objects with no attributes, which results in a MissingAttribute exception. Ordinarily, this is handled by cls.parsehost(), but in cases where a host does not contain any vulnerabilities which supply all necessary attributes, the exception is raised regardless. Annoyingly, this caused the parser to break. 😐

I added an try/except clause to handle this issue when host findings are missing required attributes and throw out the result unless strict parsing is enabled. This is not ideal, but it would be better to accept all known good hosts and throw out any anomalies rather than forcing the parser to bail out unless that is what the user wants (ie: via strict parsing).

This is a temporary fix until we can add better handling of these rogue Nessus configuration setting objects. Ultimately, the solution may be to remove this exception altogether and simply allow a greedy ingestion of all of these nessus objects, and to no longer require certain attributes. 😕

P.S. Also fixed one of my earliest mistakes when implementing the report logger. Forgot to issue it a name, which created a copy of the class instead of an instance of it. Whoops. 😅

[bmx0r]

did you try to merge it yourself?

[bmx0r]

If you want it to be deploy on pipy, you need to update the version number and tag the commit

[Script-Nomad]

I did attempt to, I don't have write access

[Script-Nomad]

In certain cases, Nessus scans which contain hosts with no information other than Nessus Configuration settings. These settings appear as "Info" vulnerability objects with no attributes, which results in a MissingAttribute exception. Ordinarily, this is handled by cls.parsehost(), but in cases where a host does not contain any vulnerabilities which supply all necessary attributes, the exception is raised regardless. Annoyingly, this caused the parser to break. 😐

I added an try/except clause to handle this issue when host findings are missing required attributes and throw out the result unless strict parsing is enabled. This is not ideal, but it would be better to accept all known good hosts and throw out any anomalies rather than forcing the parser to bail out unless that is what the user wants (ie: via strict parsing).

This is a temporary fix until we can add better handling of these rogue Nessus configuration setting objects. Ultimately, the solution may be to remove this exception altogether and simply allow a greedy ingestion of all of these nessus objects, and to no longer require certain attributes. 😕

P.S. Also fixed one of my earliest mistakes when implementing the report logger. Forgot to issue it a name, which created a copy of the class instead of an instance of it. Whoops. 😅

[bmx0r]

did you try to merge it yourself?

[bmx0r]

If you want it to be deploy on pipy, you need to update the version number and tag the commit

[Script-Nomad]

I did attempt to, I don't have write access

[Script-Nomad]

In certain cases, Nessus scans which contain hosts with no information other than Nessus Configuration settings. These settings appear as "Info" vulnerability objects with no attributes, which results in a MissingAttribute exception. Ordinarily, this is handled by cls.parsehost(), but in cases where a host does not contain any vulnerabilities which supply all necessary attributes, the exception is raised regardless. Annoyingly, this caused the parser to break. 😐

I added an try/except clause to handle this issue when host findings are missing required attributes and throw out the result unless strict parsing is enabled. This is not ideal, but it would be better to accept all known good hosts and throw out any anomalies rather than forcing the parser to bail out unless that is what the user wants (ie: via strict parsing).

This is a temporary fix until we can add better handling of these rogue Nessus configuration setting objects. Ultimately, the solution may be to remove this exception altogether and simply allow a greedy ingestion of all of these nessus objects, and to no longer require certain attributes. 😕

P.S. Also fixed one of my earliest mistakes when implementing the report logger. Forgot to issue it a name, which created a copy of the class instead of an instance of it. Whoops. 😅

[bmx0r]

did you try to merge it yourself?

[bmx0r]

If you want it to be deploy on pipy, you need to update the version number and tag the commit

[Script-Nomad]

I did attempt to, I don't have write access

[Script-Nomad]

In certain cases, Nessus scans which contain hosts with no information other than Nessus Configuration settings. These settings appear as "Info" vulnerability objects with no attributes, which results in a MissingAttribute exception. Ordinarily, this is handled by cls.parsehost(), but in cases where a host does not contain any vulnerabilities which supply all necessary attributes, the exception is raised regardless. Annoyingly, this caused the parser to break. 😐

I added an try/except clause to handle this issue when host findings are missing required attributes and throw out the result unless strict parsing is enabled. This is not ideal, but it would be better to accept all known good hosts and throw out any anomalies rather than forcing the parser to bail out unless that is what the user wants (ie: via strict parsing).

This is a temporary fix until we can add better handling of these rogue Nessus configuration setting objects. Ultimately, the solution may be to remove this exception altogether and simply allow a greedy ingestion of all of these nessus objects, and to no longer require certain attributes. 😕

P.S. Also fixed one of my earliest mistakes when implementing the report logger. Forgot to issue it a name, which created a copy of the class instead of an instance of it. Whoops. 😅

[bmx0r]

did you try to merge it yourself?

[bmx0r]

If you want it to be deploy on pipy, you need to update the version number and tag the commit

[Script-Nomad]

I did attempt to, I don't have write access

[Script-Nomad]

In certain cases, Nessus scans which contain hosts with no information other than Nessus Configuration settings. These settings appear as "Info" vulnerability objects with no attributes, which results in a MissingAttribute exception. Ordinarily, this is handled by cls.parsehost(), but in cases where a host does not contain any vulnerabilities which supply all necessary attributes, the exception is raised regardless. Annoyingly, this caused the parser to break. 😐

I added an try/except clause to handle this issue when host findings are missing required attributes and throw out the result unless strict parsing is enabled. This is not ideal, but it would be better to accept all known good hosts and throw out any anomalies rather than forcing the parser to bail out unless that is what the user wants (ie: via strict parsing).

This is a temporary fix until we can add better handling of these rogue Nessus configuration setting objects. Ultimately, the solution may be to remove this exception altogether and simply allow a greedy ingestion of all of these nessus objects, and to no longer require certain attributes. 😕

P.S. Also fixed one of my earliest mistakes when implementing the report logger. Forgot to issue it a name, which created a copy of the class instead of an instance of it. Whoops. 😅

[bmx0r]

did you try to merge it yourself?

[bmx0r]

If you want it to be deploy on pipy, you need to update the version number and tag the commit

[Script-Nomad]

I did attempt to, I don't have write access

[Script-Nomad]

In certain cases, Nessus scans which contain hosts with no information other than Nessus Configuration settings. These settings appear as "Info" vulnerability objects with no attributes, which results in a MissingAttribute exception. Ordinarily, this is handled by cls.parsehost(), but in cases where a host does not contain any vulnerabilities which supply all necessary attributes, the exception is raised regardless. Annoyingly, this caused the parser to break. 😐

I added an try/except clause to handle this issue when host findings are missing required attributes and throw out the result unless strict parsing is enabled. This is not ideal, but it would be better to accept all known good hosts and throw out any anomalies rather than forcing the parser to bail out unless that is what the user wants (ie: via strict parsing).

This is a temporary fix until we can add better handling of these rogue Nessus configuration setting objects. Ultimately, the solution may be to remove this exception altogether and simply allow a greedy ingestion of all of these nessus objects, and to no longer require certain attributes. 😕

P.S. Also fixed one of my earliest mistakes when implementing the report logger. Forgot to issue it a name, which created a copy of the class instead of an instance of it. Whoops. 😅

[bmx0r]

did you try to merge it yourself?

[bmx0r]

If you want it to be deploy on pipy, you need to update the version number and tag the commit

[Script-Nomad]

I did attempt to, I don't have write access

[Script-Nomad]

In certain cases, Nessus scans which contain hosts with no information other than Nessus Configuration settings. These settings appear as "Info" vulnerability objects with no attributes, which results in a MissingAttribute exception. Ordinarily, this is handled by cls.parsehost(), but in cases where a host does not contain any vulnerabilities which supply all necessary attributes, the exception is raised regardless. Annoyingly, this caused the parser to break. 😐

I added an try/except clause to handle this issue when host findings are missing required attributes and throw out the result unless strict parsing is enabled. This is not ideal, but it would be better to accept all known good hosts and throw out any anomalies rather than forcing the parser to bail out unless that is what the user wants (ie: via strict parsing).

This is a temporary fix until we can add better handling of these rogue Nessus configuration setting objects. Ultimately, the solution may be to remove this exception altogether and simply allow a greedy ingestion of all of these nessus objects, and to no longer require certain attributes. 😕

P.S. Also fixed one of my earliest mistakes when implementing the report logger. Forgot to issue it a name, which created a copy of the class instead of an instance of it. Whoops. 😅

[bmx0r]

did you try to merge it yourself?

[bmx0r]

If you want it to be deploy on pipy, you need to update the version number and tag the commit

[Script-Nomad]

I did attempt to, I don't have write access

[Script-Nomad]

In certain cases, Nessus scans which contain hosts with no information other than Nessus Configuration settings. These settings appear as "Info" vulnerability objects with no attributes, which results in a MissingAttribute exception. Ordinarily, this is handled by cls.parsehost(), but in cases where a host does not contain any vulnerabilities which supply all necessary attributes, the exception is raised regardless. Annoyingly, this caused the parser to break. 😐

I added an try/except clause to handle this issue when host findings are missing required attributes and throw out the result unless strict parsing is enabled. This is not ideal, but it would be better to accept all known good hosts and throw out any anomalies rather than forcing the parser to bail out unless that is what the user wants (ie: via strict parsing).

This is a temporary fix until we can add better handling of these rogue Nessus configuration setting objects. Ultimately, the solution may be to remove this exception altogether and simply allow a greedy ingestion of all of these nessus objects, and to no longer require certain attributes. 😕

P.S. Also fixed one of my earliest mistakes when implementing the report logger. Forgot to issue it a name, which created a copy of the class instead of an instance of it. Whoops. 😅

[bmx0r]

did you try to merge it yourself?

[bmx0r]

If you want it to be deploy on pipy, you need to update the version number and tag the commit

[Script-Nomad]

I did attempt to, I don't have write access