CVE-2011-4897
published 2011-12-23CVE-2011-4897: Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option, uses the local hostname as the Nickname value, which allows…
PriorityP415medium4.3CVSS 2.0
AVNACMAuNCPINAN
EPSS
1.62%
73.3th percentile
Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option, uses the local hostname as the Nickname value, which allows remote attackers to obtain potentially sensitive information by reading this value.
Affected
209 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | tor | < tor 0.2.2.27-beta-1 (bookworm) | tor 0.2.2.27-beta-1 (bookworm) |
| tor | tor | <= 0.2.2.24 | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
| tor | tor | — | — |
CVSS provenance
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:P/I:N/A:N
osv4.3MEDIUM
vendor_debian4.3LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-7h3x-gchg-chhg: Tor before 0
ghsa_unreviewed·2022-05-17
CVE-2011-4897 [MEDIUM] CWE-200 GHSA-7h3x-gchg-chhg: Tor before 0
Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option, uses the local hostname as the Nickname value, which allows remote attackers to obtain potentially sensitive information by reading this value.
OSV
CVE-2011-4897: Tor before 0
osv·2011-12-23·CVSS 4.3
CVE-2011-4897 [MEDIUM] CVE-2011-4897: Tor before 0
Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option, uses the local hostname as the Nickname value, which allows remote attackers to obtain potentially sensitive information by reading this value.
Debian
CVE-2011-4897: tor - Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname confi...
vendor_debian·2011·CVSS 4.3
CVE-2011-4897 [MEDIUM] CVE-2011-4897: tor - Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname confi...
Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option, uses the local hostname as the Nickname value, which allows remote attackers to obtain potentially sensitive information by reading this value.
Scope: local
bookworm: resolved (fixed in 0.2.2.27-beta-1)
bullseye: resolved (fixed in 0.2.2.27-beta-1)
forky: resolved (fixed in 0.2.2.27-beta-1)
sid: resolved (fixed in 0.2.2.27-beta-1)
trixie: resolved (fixed in 0.2.2.27-beta-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2011-2778 CVE-2011-4897 tor various flaws [epel-5]
bugzilla·2012-12-11·CVSS 7.6
CVE-2011-2778 [HIGH] CVE-2011-2778 CVE-2011-4897 tor various flaws [epel-5]
CVE-2011-2778 CVE-2011-4897 tor various flaws [epel-5]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora EPEL.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When creating a Bodhi update request, please use the bodhi submission link
noted in the next comment(s). This will include the bug IDs of this
tracking bug as well as the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
Bodhi notes field when available.
epel-5 tracking bug for tor: see blocks bug l
Bugzilla
CVE-2011-4897 Tor Nickname information disclosure [fedora-all]
bugzilla·2012-01-11·CVSS 4.3
CVE-2011-4897 [MEDIUM] CVE-2011-4897 Tor Nickname information disclosure [fedora-all]
CVE-2011-4897 Tor Nickname information disclosure [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected Fedora
versions.
For comments that are specific to the vulnerability please use bugs filed
against "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When creating a Bodhi update request, please include this bug ID and the
bug IDs of this bug's parent bugs filed against the "Security Response"
product (the top-level CVE bugs). Please mention the CVE IDs being fixed
in the RPM changelog when available.
Bodhi update submission link:
https://admin.fedoraproject.org/updates/new/?type_=security&bugs=770018
Bugzilla
CVE-2011-4897 Tor Nickname information disclosure
bugzilla·2011-12-23·CVSS 4.3
CVE-2011-4897 [MEDIUM] CVE-2011-4897 Tor Nickname information disclosure
CVE-2011-4897 Tor Nickname information disclosure
https://blog.torproject.org/blog/tor-02225-alpha-out
Tor before 0.2.2.25-alpha, when configured as a relay without the
Nickname configuration option, uses the local hostname as the Nickname
value, which allows remote attackers to obtain potentially sensitive
information by reading this value.
Discussion:
Created tor tracking bugs for this issue
Affects: fedora-all [bug 773452]
---
Created tor tracking bugs for this issue
Affects: epel-5 [bug 885974]
---
Current EPEL and Fedora provide 0.2.3.25 which includes this fix.
arXiv
One Bad Apple Spoils the Barrel: Understanding the Security Risks Introduced by Third-Party Components in IoT Firmware
arxiv_fulltext·2022-12-29
One Bad Apple Spoils the Barrel: Understanding the Security Risks Introduced by Third-Party Components in IoT Firmware
One Bad Apple Spoils the Barrel: Understanding the Security Risks Introduced by Third-Party Components in IoT Firmware
## Abstract
Currently, the development of IoT firmware heavily depends on third-party components (TPCs) to improve development efficiency. Nevertheless, TPCs are not secure, and the vulnerabilities in TPCs will influence the security of IoT firmware. Existing works pay less attention to the vulnerabilities caused by TPCs, and we still lack a comprehensive understanding of the security impact of TPC vulnerability against firmware. To fill in the knowledge gap, we design and implement , which leverages syntactical features and control-flow graph features to detect the TPCs in firmware, and then recognizes the corresponding vulnerabilities. Based on , we present the first l
2011-12-23
Published